Bandwidth Part Management in a Wireless System

ABSTRACT

A method may include transmitting, by a base station to a wireless device via a physical downlink control channel (PDCCH), a downlink control information (DCI) indicating for the wireless device to switch from a second bandwidth part (BWP) to a first BWP as an active BWP. The method may include receiving, in response to the first BWP being activated, a reference signal received power (RSRP) report for the first BWP. The RSRP report may include a reference signal index indicating a reference signal of the first BWP, and a value of an RSRP of the reference signal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/857,632, filed Apr. 24, 2020, which is a continuation ofInternational Application No. PCT/US2018/058395, filed Oct. 31, 2018,which claims the benefit of U.S. Provisional Application No. 62/577,542,filed Oct. 26, 2017, and U.S. Provisional Application No. 62/577,800,filed Oct. 27, 2017, all of which are hereby incorporated by referencein their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentdisclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present disclosure.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e)LTE eNB) as per an aspect of anembodiment of the present disclosure.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present disclosure.

FIG. 15 is an example diagram for synchronization signal blocktransmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example diagram of random access procedure when configuredwith multiple beam as per an aspect of an embodiment of the presentdisclosure.

FIG. 17 is an example diagram for channel state information referencesignal (CSI-RS) transmissions as per an aspect of an embodiment of thepresent disclosure.

FIG. 18 is an example diagram for channel state information referencesignal (CSI-RS) transmissions as per an aspect of an embodiment of thepresent disclosure.

FIG. 19 is an example diagram for downlink beam management procedures asper an aspect of an embodiment of the present disclosure.

FIG. 20A is an example diagram for downlink beam failure scenario in atransmission receiving point (TRP) as per an aspect of an embodiment ofthe present disclosure.

FIG. 20B is an example diagram for downlink beam failure scenario inmultiple TRPs as per an aspect of an embodiment of the presentdisclosure.

FIG. 21A is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 21B is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 22A is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 22B is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 23 is an example diagram for downlink control information (DCI)formats as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example diagram for bandwidth part (BWP) configurations asper an aspect of an embodiment of the present disclosure.

FIG. 25 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 26 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 27 is an example diagram for BWP inactivity timer management of BWPoperation as per an aspect of an embodiment of the present disclosure.

FIG. 28A and FIG. 28B are example flowcharts of BWP management as per anaspect of an embodiment of the present disclosure.

FIG. 29 is an example diagram for beam management of BWP operation asper an aspect of an embodiment of the present disclosure.

FIG. 30 is example diagrams illustrating scenarios maintaining a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure.

FIG. 31 is example diagrams illustrating scenarios maintaining a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure.

FIG. 32A and FIG. 32B are example flowcharts of BWP inactivity timermanagement as per an aspect of an embodiment of the present disclosure.

FIG. 33 is example diagrams illustrating scenarios maintaining a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure.

FIG. 34 is example diagrams illustrating scenarios maintaining a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure.

FIG. 35 is example diagrams illustrating scenarios maintaining a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure.

FIG. 36 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 37 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 38 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 39 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 40 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 41 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 42 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 43 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 44 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 45 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 46 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 47 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

FIG. 48 may be an example flow diagram as per an aspect of an embodimentof the present disclosure.

DETAILED DESCRIPTION

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal timing in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

CP cyclic prefix

DL downlink

DCI downlink control information

DC dual connectivity

eMB B enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NR new radio

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG resource block groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TTI transmission time interval

TB transport block

UL uplink

UE user equipment

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

CU central unit

DU distributed unit

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NSSAI network slice selection assistance information

PLMN public land mobile network

UPGW user plane gateway

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) maycomprise of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for an antenna port,and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for an antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in codewordsto be transmitted on a physical channel; modulation of scrambled bits togenerate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present disclosure. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentdisclosure. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three examples ofbearers, including, an MCG bearer, an SCG bearer and a split bearer asshown in FIG. 6. NR RRC may be located in master gNB and SRBs may beconfigured as a MCG bearer type and may use the radio resources of themaster gNB. Multi-connectivity may also be described as having at leastone bearer configured to use radio resources provided by the secondarygNB. Multi-connectivity may or may not be configured/implemented inexample embodiments of the disclosure.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g., based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprisesPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 900 to activate anSCell. A preamble 902 (Msg1) may be sent by a UE in response to a PDCCHorder 901 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 903 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 904 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e)LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three example bearers including an MCG bearer,an SCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, andFIG. 12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the disclosure.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g., based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present disclosure. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, a DU may be configured with a differentsplit, and a CU may provide different split options for different DUs.In per UE split, a gNB (CU and DU) may provide different split optionsfor different UEs. In per bearer split, different split options may beutilized for different bearer types. In per slice splice, differentsplit options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured, and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by wireless devices; time & frequencysynchronization of wireless devices.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the basestation transmissions may start only at the subframe boundary. LAA maysupport transmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme (e.g. by using different LBTmechanisms or parameters) for example, since the LAA UL is based onscheduled access which affects a wireless device's channel contentionopportunities. Other considerations motivating a different UL LBT schemeinclude, but are not limited to, multiplexing of multiple wirelessdevices in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from awireless device perspective may be a continuous transmission from awireless device with no transmission immediately before or after fromthe same wireless device on the same CC. In an example, UL transmissionburst is defined from a wireless device perspective. In an example, anUL transmission burst may be defined from a base station perspective. Inan example, in case of a base station operating DL+UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. For example, an instant in time may be part of a DLtransmission burst or an UL transmission burst.

A New Radio (NR) system may support both single beam and multi-beamoperations. In a multi-beam system, a base station (e.g., gNB) mayperform a downlink beam sweeping to provide coverage for downlinkSynchronization Signals (SSs) and common control channels. A UserEquipment (UE) may perform an uplink beam sweeping for uplink directionto access a cell. In a single beam scenario, a gNB may configuretime-repetition transmission for one SS block, which may comprise atleast Primary Synchronization Signal (PSS), Secondary SynchronizationSignal (SSS), and Physical Broadcast Channel (PBCH), with a wide beam.In a multi-beam scenario, a gNB may configure at least some of thesesignals and physical channels in multiple beams. A UE may identify atleast OFDM symbol index, slot index in a radio frame and radio framenumber from an SS block.

In an example, in an RRC_INACTIVE state or RRC_IDLE state, a UE mayassume that SS blocks form an SS burst, and an SS burst set. An SS burstset may have a given periodicity. In multi-beam scenarios, SS blocks maybe transmitted in multiple beams, together forming an SS burst. One ormore SS blocks may be transmitted on one beam. A beam has a steeringdirection. If multiple SS bursts are transmitted with beams, these SSbursts together may form an SS burst set as shown in FIG. 15. A basestation 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to 1502Hduring time periods 1503. A plurality of these SS bursts may comprise anSS burst set, such as an SS burst set 1504 (e.g., SS bursts 1502A and1502E). An SS burst set may comprise any number of a plurality of SSbursts 1502A to 1502H. Each SS burst within an SS burst set maytransmitted at a fixed or variable periodicity during time periods 1503.

An SS may be based on Cyclic Prefix-Orthogonal Frequency DivisionMultiplexing (CP-OFDM). The SS may comprise at least two types ofsynchronization signals; NR-PSS (Primary synchronization signal) andNR-SSS (Secondary synchronization signal). NR-PSS may be defined atleast for initial symbol boundary synchronization to the NR cell. NR-SSSmay be defined for detection of NR cell ID or at least part of NR cellID. NR-SSS detection may be based on the fixed time/frequencyrelationship with NR-PSS resource position irrespective of duplex modeand beam operation type at least within a given frequency range and CPoverhead. Normal CP may be supported for NR-PSS and NR-SSS.

The NR may comprise at least one physical broadcast channel (NR-PBCH).When a gNB transmit (or broadcast) the NR-PBCH, a UE may decode theNR-PBCH based on the fixed relationship with NR-PSS and/or NR-SSSresource position irrespective of duplex mode and beam operation type atleast within a given frequency range and CP overhead. NR-PBCH may be anon-scheduled broadcast channel carrying at least a part of minimumsystem information with fixed payload size and periodicity predefined inthe specification depending on carrier frequency range.

In single beam and multi-beam scenarios, NR may comprise an SS blockthat may support time (frequency, and/or spatial) division multiplexingof NR-PSS, NR-SSS, and NR-PBCH. A gNB may transmit NR-PSS, NR-SSS and/orNR-PBCH within an SS block. For a given frequency band, an SS block maycorrespond to N OFDM symbols based on the default subcarrier spacing,and N may be a constant. The signal multiplexing structure may be fixedin NR. A wireless device may identify, e.g., from an SS block, an OFDMsymbol index, a slot index in a radio frame, and a radio frame numberfrom an SS block.

A NR may support an SS burst comprising one or more SS blocks. An SSburst set may comprise one or more SS bursts. For example, a number ofSS bursts within a SS burst set may be finite. From physical layerspecification perspective, NR may support at least one periodicity of SSburst set. From UE perspective, SS burst set transmission may beperiodic, and UE may assume that a given SS block is repeated with an SSburst set periodicity.

Within an SS burst set periodicity, NR-PBCH repeated in one or more SSblocks may change. A set of possible SS block time locations may bespecified per frequency band in an RRC message. The maximum number ofSS-blocks within SS burst set may be carrier frequency dependent. Theposition(s) of actual transmitted SS-blocks may be informed at least forhelping CONNECTED/IDLE mode measurement, for helping CONNECTED mode UEto receive downlink (DL) data/control in one or more SS-blocks, or forhelping IDLE mode UE to receive DL data/control in one or moreSS-blocks. A UE may not assume that the gNB transmits the same number ofphysical beam(s). A UE may not assume the same physical beam(s) acrossdifferent SS-blocks within an SS burst set. For an initial cellselection, UE may assume default SS burst set periodicity which may bebroadcast via an RRC message and frequency band-dependent. At least formulti-beams operation case, the time index of SS-block may be indicatedto the UE.

For CONNECTED and IDLE mode UEs, NR may support network indication of SSburst set periodicity and information to derive measurementtiming/duration (e.g., time window for NR-SS detection). A gNB mayprovide (e.g., via broadcasting an RRC message) one SS burst setperiodicity information per frequency carrier to UE and information toderive measurement timing/duration if possible. In case that one SSburst set periodicity and one information regarding timing/duration areindicated, a UE may assume the periodicity and timing/duration for allcells on the same carrier. If a gNB does not provide indication of SSburst set periodicity and information to derive measurementtiming/duration, a UE may assume a predefined periodicity, e.g., 5 ms,as the SS burst set periodicity. NR may support set of SS burst setperiodicity values for adaptation and network indication.

For initial access, a UE may assume a signal corresponding to a specificsubcarrier spacing of NR-PSS/SSS in a given frequency band given by a NRspecification. For NR-PSS, a Zadoff-Chu (ZC) sequence may be employed asa sequence for NR-PSS. NR may define at least one basic sequence lengthfor a SS in case of sequence-based SS design. The number of antenna portof NR-PSS may be 1. For NR-PBCH transmission, NR may support a fixednumber of antenna port(s). A UE may not be required for a blinddetection of NR-PBCH transmission scheme or number of antenna ports. AUE may assume the same PBCH numerology as that of NR-SS. For the minimumsystem information delivery, NR-PBCH may comprise a part of minimumsystem information. NR-PBCH contents may comprise at least a part of theSFN (system frame number) or CRC. A gNB may transmit the remainingminimum system information in shared downlink channel via NR-PDSCH.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may berepeated for a cell, e.g., to support cell selection, cell reselection,and/or initial access procedures. For an SS burst, an associated PBCH ora physical downlink shared channel (PDSCH) scheduling system informationmay be broadcasted by a base station to multiple wireless devices. ThePDSCH may be indicated by a physical downlink control channel (PDCCH) ina common search space. The system information may comprise a physicalrandom access channel (PRACH) configuration for a beam. For a beam, abase station (e.g., a gNB in NR) may have a RACH configuration which mayinclude a PRACH preamble pool, time and/or frequency radio resources,and other power related parameters. A wireless device may use a PRACHpreamble from a RACH configuration to initiate a contention-based RACHprocedure or a contention-free RACH procedure. A wireless device mayperform a 4-step RACH procedure, which may be a contention-based RACHprocedure or a contention-free RACH procedure. The wireless device mayselect a beam associated with an SS block that may have the bestreceiving signal quality. The wireless device may successfully detect acell identifier associated with the cell and decode system informationwith a RACH configuration. The wireless device may use one PRACHpreamble and select one PRACH resource from RACH resources indicated bythe system information associated with the selected beam. A PRACHresource may comprise at least one of: a PRACH index indicating a PRACHpreamble, a PRACH format, a PRACH numerology, time and/or frequencyradio resource allocation, power setting of a PRACH transmission, and/orother radio resource parameters. For a contention-free RACH procedure,the PRACH preamble and resource may be indicated in a DCI or other highlayer signaling.

FIG. 16 shows an example of a random access procedure (e.g., via a RACH)that may include sending, by a base station, one or more SS blocks. Awireless device 1620 (e.g., a UE) may transmit one or more preambles toa base station 1621 (e.g., a gNB in NR). Each preamble transmission bythe wireless device may be associated with a separate random accessprocedure, such as shown in FIG. 16. The random access procedure maybegin at step 1601 with a base station 1621 (e.g., a gNB in NR) sendinga first SS block to a wireless device 1621 (e.g., a UE). Any of the SSblocks may comprise one or more of a PSS, SSS, tertiary synchronizationsignal (TSS), or PBCH signal. The first SS block in step 1601 may beassociated with a first PRACH configuration. At step 1602, the basestation 1621 may send to the wireless device 1620 a second SS block thatmay be associated with a second PRACH configuration. At step 1603, thebase station 1621 may send to the wireless device 1620 a third SS blockthat may be associated with a third PRACH configuration. At step 1604,the base station 1621 may send to the wireless device 1620 a fourth SSblock that may be associated with a fourth PRACH configuration. Anynumber of SS blocks may be sent in the same manner in addition to, orreplacing, steps 1603 and 1604. An SS burst may comprise any number ofSS blocks. For example, SS burst 1610 comprises the three SS blocks sentduring steps 1602-1604.

The wireless device 1620 may send to the base station 1621 a preamble,at step 1605, e.g., after or in response to receiving one or more SSblocks or SS bursts. The preamble may comprise a PRACH preamble, and maybe referred to as RA Msg 1. The PRACH preamble may be transmitted instep 1605 according to or based on a PRACH configuration that may bereceived in an SS block (e.g., one of the SS blocks from steps1601-1604) that may be determined to be the best SS block beam. Thewireless device 1620 may determine a best SS block beam from among SSblocks it may receive prior to sending the PRACH preamble. The basestation 1621 may send a random access response (RAR), which may bereferred to as RA Msg2, at step 1606, e.g., after or in response toreceiving the PRACH preamble. The RAR may be transmitted in step 1606via a DL beam that corresponds to the SS block beam associated with thePRACH configuration. The base station 1621 may determine the best SSblock beam from among SS blocks it previously sent prior to receivingthe PRACH preamble. The base station 1621 may receive the PRACH preambleaccording to or based on the PRACH configuration associated with thebest SS block beam.

The wireless device 1620 may send to the base station 1621 anRRCConnectionRequest and/or RRCConnectionResumeRequest message, whichmay be referred to as RA Msg3, at step 1607, e.g., after or in responseto receiving the RAR. The base station 1621 may send to the wirelessdevice 1620 an RRCConnectionSetup and/or RRCConnectionResume message,which may be referred to as RA Msg4, at step 1608, e.g., after or inresponse to receiving the RRCConnectionRequest and/orRRCConnectionResumeRequest message. The wireless device 1620 may send tothe base station 1621 an RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message, which may be referred to as RAMsg5, at step 1609, e.g., after or in response to receiving theRRCConnectionSetup and/or RRCConnectionResume. An RRC connection may beestablished between the wireless device 1620 and the base station 1621,and the random access procedure may end, e.g., after or in response toreceiving the RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may bedetermined based on a channel state information reference signal(CSI-RS). A wireless device may use a CSI-RS in a multi-beam system forestimating the beam quality of the links between the wireless device anda base station. For example, based on a measurement of a CSI-RS, awireless device may report CSI for downlink channel adaption. A CSIparameter may include a precoding matrix index (PMI), a channel qualityindex (CQI) value, and/or a rank indicator (RI). A wireless device mayreport a beam index based on a reference signal received power (RSRP)measurement on a CSI-RS. The wireless device may report the beam indexin a CSI resource indication (CRI) for downlink beam selection. A basestation may transmit a CSI-RS via a CSI-RS resource, such as via one ormore antenna ports, or via one or more time and/or frequency radioresources. A beam may be associated with a CSI-RS. A CSI-RS may comprisean indication of a beam direction. Each of a plurality of beams may beassociated with one of a plurality of CSI-RSs. A CSI-RS resource may beconfigured in a cell-specific way, e.g., via common RRC signaling.Additionally or alternatively, a CSI-RS resource may be configured in awireless device-specific way, e.g., via dedicated RRC signaling and/orlayer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices inor served by a cell may measure a cell-specific CSI-RS resource. Adedicated subset of wireless devices in or served by a cell may measurea wireless device-specific CSI-RS resource. A base station may transmita CSI-RS resource periodically, using aperiodic transmission, or using amulti-shot or semi-persistent transmission. In a periodic transmission,a base station may transmit the configured CSI-RS resource using aconfigured periodicity in the time domain. In an aperiodic transmission,a base station may transmit the configured CSI-RS resource in adedicated time slot. In a multi-shot or semi-persistent transmission, abase station may transmit the configured CSI-RS resource in a configuredperiod. A base station may configure different CSI-RS resources indifferent terms for different purposes. Different terms may include,e.g., cell-specific, device-specific, periodic, aperiodic, multi-shot,or other terms. Different purposes may include, e.g., beam management,CQI reporting, or other purposes.

FIG. 17 shows an example of transmitting CSI-RSs periodically for abeam. A base station 1701 may transmit a beam in a predefined order inthe time domain, such as during time periods 1703. Beams used for aCSI-RS transmission, such as for CSI-RS 1704 in transmissions 1702Cand/or 1703E, may have a different beam width relative to a beam widthfor SS-blocks transmission, such as for SS blocks 1702A, 1702B, 1702D,and 1702F-1702H. Additionally or alternatively, a beam width of a beamused for a CSI-RS transmission may have the same value as a beam widthfor an SS block. Some or all of one or more CSI-RSs may be included inone or more beams. An SS block may occupy a number of OFDM symbols(e.g., 4), and a number of subcarriers (e.g., 240), carrying asynchronization sequence signal. The synchronization sequence signal mayidentify a cell.

FIG. 18 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 18 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 18 shows three beams that may be configured for a wireless device,e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in a RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin a RB of a third symbol. All subcarriers in a RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs), such as shown in FIG. 20A and FIG. 20B,respectively.

FIG. 19 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), e.g., tosupport a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, e.g., anintra-TRP and/or inter-TRP Tx beam sweep from a set of different beams(shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device 1901, may include, e.g., a wireless device Rx beamsweep from a set of different beams (shown, in the bottom rows of P1 andP3, as ovals rotated in a clockwise direction indicated by the dashedarrow). Procedure P2 may be used to enable a wireless device measurementon different Tx beams of a TRP (or multiple TRPs) (shown, in the top rowof P2, as ovals rotated in a counter-clockwise direction indicated bythe dashed arrow), e.g., which may change inter-TRP and/or intra-TRP Txbeam(s). Procedure P2 may be performed, e.g., on a smaller set of beamsfor beam refinement than in procedure P1. P2 may be a particular exampleof P1. Procedure P3 may be used to enable a wireless device measurementon the same Tx beam (shown as oval in P3), e.g., to change a wirelessdevice Rx beam if the wireless device 1901 uses beamforming.

A wireless device 1901 (e.g., a UE) and/or a base station 1902 (e.g., agNB) may trigger a beam failure recovery mechanism. The wireless device1901 may trigger a beam failure recovery (BFR) request transmission,e.g., if a beam failure event occurs. A beam failure event may include,e.g., a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory. A determination of anunsatisfactory quality of beam pair link(s) of an associated channel maybe based on the quality falling below a threshold and/or an expirationof a timer.

The wireless device 1901 may measure a quality of beam pair link(s)using one or more reference signals (RS). One or more SS blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. Each of the one or more CSI-RS resources may be associatedwith a CSI-RS resource index (CRI). A quality of a beam pair link may bebased on one or more of an RSRP value, reference signal received quality(RSRQ) value, and/or CSI value measured on RS resources. The basestation 1902 may indicate that an RS resource, e.g., that may be usedfor measuring a beam pair link quality, is quasi-co-located (QCLed) withone or more DM-RSs of a control channel. The RS resource and the DM-RSsof the control channel may be QCLed when the channel characteristicsfrom a transmission via an RS to the wireless device 1901, and thechannel characteristics from a transmission via a control channel to thewireless device, are similar or the same under a configured criterion.

FIG. 20A shows an example of a beam failure event involving a singleTRP. A single TRP such as at a base station 2001 may transmit, to awireless device 2002, a first beam 2003 and a second beam 2004. A beamfailure event may occur if, e.g., a serving beam, such as the secondbeam 2004, is blocked by a moving vehicle 2005 or other obstruction(e.g., building, tree, land, or any object) and configured beams (e.g.,the first beam 2003 and/or the second beam 2004), including the servingbeam, are received from the single TRP. The wireless device 2002 maytrigger a mechanism to recover from beam failure when a beam failureoccurs.

FIG. 20B shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 2006 and at asecond base station 2009, may transmit, to a wireless device 2008, afirst beam 2007 (e.g., from the first base station 2006) and a secondbeam 2010 (e.g., from the second base station 2009). A beam failureevent may occur when, e.g., a serving beam, such as the second beam2010, is blocked by a moving vehicle 2011 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 2007 and/or the second beam 2010) are received from multipleTRPs. The wireless device 2008 may trigger a mechanism to recover frombeam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M≥1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channel.Signaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, e.g.,via an uplink physical channel or signal, a base station may detect thatthere is a beam failure event, for the wireless device, by monitoringthe uplink physical channel or signal. The base station may initiate abeam recovery mechanism to recover the beam pair link for transmittingPDCCH between the base station and the wireless device. The base stationmay transmit one or more control signals, to the wireless device, e.g.,after or in response to receiving the beam failure recovery request. Abeam recovery mechanism may be, e.g., an L1 scheme, or a higher layerscheme.

A base station may transmit one or more messages comprising, e.g.,configuration parameters of an uplink physical channel and/or a signalfor transmitting a beam failure recovery request. The uplink physicalchannel and/or signal may be based on at least one of the following: anon-contention based PRACH (e.g., a beam failure recovery PRACH orBFR-PRACH), which may use a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

A gNB may respond a confirmation message to a UE after receiving one ormultiple BFR request. The confirmation message may include the CRIassociated with the candidate beam the UE indicates in the one ormultiple BFR request. The confirmation message may be a L1 controlinformation.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells).

When configured with CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a gNB may transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). In anexample, a wireless device may deactivate an SCell in response to anexpiry of the SCell timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising: SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell. The wireless devicemay start or restart the first SCell timer in the slot when the SCellActivation/Deactivation MAC CE activating the SCell has been received.In an example, in response to the activating the SCell, the wirelessdevice may (re-)initialize one or more suspended configured uplinkgrants of a configured grant Type 1 associated with the SCell accordingto a stored configuration. In an example, in response to the activatingthe SCell, the wireless device may trigger PHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart a first SCell timer (e.g., sCellDeactivationTimer)associated with the activated SCell. In an example, when at least onesecond PDCCH on a serving cell (e.g. a PCell or an SCell configured withPUCCH, i.e. PUCCH SCell) scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell, awireless device may restart the first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

FIG. 21A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’)may identify the SCell Activation/Deactivation MAC CE of one octet. TheSCell Activation/Deactivation MAC CE of one octet may have a fixed size.The SCell Activation/Deactivation MAC CE of one octet may comprise asingle octet. The single octet may comprise a first number of C-fields(e.g. seven) and a second number of R-fields (e.g., one).

FIG. 21B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’) may identify the SCell Activation/Deactivation MAC CE of fouroctets. The SCell Activation/Deactivation MAC CE of four octets may havea fixed size. The SCell Activation/Deactivation MAC CE of four octetsmay comprise four octets. The four octets may comprise a third number ofC-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

In FIG. 21A and/or FIG. 21B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 21A and FIG. 21B, an R field may indicate a reserved bit.The R field may be set to zero.

FIG. 22A and FIG. 22B show timeline when a UE receives a MAC activationcommand. When a UE receives a MAC activation command for a secondarycell in subframe n, the corresponding actions in the MAC layer shall beapplied no later than the minimum requirement defined in 3GPP TS 36.133or TS 38.133 and no earlier than subframe n+8, except for the following:the actions related to CSI reporting and the actions related to thesCellDeactivationTimer associated with the secondary cell, which shallbe applied in subframe n+8. When a UE receives a MAC deactivationcommand for a secondary cell or the sCellDeactivationTimer associatedwith the secondary cell expires in subframe n, the corresponding actionsin the MAC layer shall apply no later than the minimum requirementdefined in 3GPP TS 36.133 or TS 38.133, except for the actions relatedto CSI reporting which shall be applied in subframe n+8.

When a UE receives a MAC activation command for a secondary cell insubframe n, the actions related to CSI reporting and the actions relatedto the sCellDeactivationTimer associated with the secondary cell, areapplied in subframe n+8. When a UE receives a MAC deactivation commandfor a secondary cell or other deactivation conditions are met (e.g. thesCellDeactivationTimer associated with the secondary cell expires) insubframe n, the actions related to CSI reporting are applied in subframen+8. The UE starts reporting invalid or valid CSI for the Scell at the(n+8)^(th) subframe, and start or restart the sCellDeactivationTimerwhen receiving the MAC CE activating the SCell in the n^(th) subframe.For some UE having slow activation, it may report an invalid CSI(out-of-range CSI) at the (n+8)^(th) subframe, for some UE having aquick activation, it may report a valid CSI at the (n+8)^(th) subframe.

When a UE receives a MAC activation command for an SCell in subframe n,the UE starts reporting CQI/PMI/RI/PTI for the SCell at subframe n+8 andstarts or restarts the sCellDeactivationTimer associated with the SCellat subframe n+8. It is important to define the timing of these actionsfor both UE and eNB. For example, sCellDeactivationTimer is maintainedin both eNB and UE and it is important that both UE and eNB stop, startand/or restart this timer in the same TTI. Otherwise, thesCellDeactivationTimer in the UE may not be in-sync with thecorresponding sCellDeactivationTimer in the eNB. Also, eNB startsmonitoring and receiving CSI (CQI/PMI/RI/PTI) according to thepredefined timing in the same TTI and/or after UE starts transmittingthe CSI. If the CSI timings in UE and eNB are not coordinated based on acommon standard or air interface signaling the network operation mayresult in inefficient operations and/or errors.

FIG. 23 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In an example, a gNB may transmit a DCI via a PDCCH forscheduling decision and power-control commends. More specifically, theDCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

The different types of control information correspond to different DCImessage sizes. For example, supporting spatial multiplexing withnoncontiguous allocation of RBs in the frequency domain may require alarger scheduling message in comparison with an uplink grant allowingfor frequency-contiguous allocation only. The DCI may be categorizedinto different DCI formats, where a format corresponds to a certainmessage size and usage.

In an example, a UE may monitor one or more PDCCH to detect one or moreDCI with one or more DCI format. The one or more PDCCH may betransmitted in common search space or UE-specific search space. A UE maymonitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the information in the DCI formats used for downlinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In a NR system, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets. A gNB maytransmit one or more RRC message comprising configuration parameters ofone or more control resource sets. At least one of the one or morecontrol resource sets may comprise at least one of: a first OFDM symbol;a number of consecutive OFDM symbols; a set of resource blocks; aCCE-to-REG mapping; and a REG bundle size, in case of interleavedCCE-to-REG mapping.

Example of Bandwidth Part Management

FIG. 24 shows example of multiple BWP configuration. A gNB may transmitone or more message comprising configuration parameters of one or morebandwidth parts (BWP). The one or more BWPs may have differentnumerologies. A gNB may transmit one or more control information forcross-BWP scheduling to a UE. One BWP may overlap with another BWP infrequency domain.

A gNB may transmit one or more messages comprising configurationparameters of one or more DL and/or UL BWPs for a cell, with at leastone BWP as the active DL or UL BWP, and zero or one BWP as the defaultDL or UL BWP. For the PCell, the active DL BWP may be the DL BWP onwhich the UE may monitor one or more PDCCH, and/or receive PDSCH. Theactive UL BWP is the UL BWP on which the UE may transmit uplink signal.For a secondary cell (SCell) if configured, the active DL BWP may be theDL BWP on which the UE may monitor one or more PDCCH and receive PDSCHwhen the SCell is activated by receiving a MAC activation/deactivationCE. The active UL BWP is the UL BWP on which the UE may transmit PUCCH(if configured) and/or PUSCH when the SCell is activated by receiving aMAC activation/deactivation CE. Configuration of multiple BWPs may beused to save UE's power consumption. When configured with an active BWPand a default BWP, a UE may switch to the default BWP if there is noactivity on the active BWP. For example, a default BWP may be configuredwith narrow bandwidth, an active BWP may be configured with widebandwidth. If there is no signal transmitting or receiving, the UE mayswitch the BWP to the default BWP, which may reduce power consumption.

Switching BWP may be triggered by a DCI or a timer. When a UE receives aDCI indicating DL BWP switching from an active BWP to a new BWP, the UEmay monitor PDCCH and/or receive PDSCH on the new BWP. When the UEreceives a DCI indicating UL BWP switching from an active BWP to a newBWP, the UE may transmit PUCCH (if configured) and/or PUSCH on the newBWP. A gNB may transmit one or more messages comprising a BWP inactivitytimer to a UE. The UE starts the timer when it switches its active DLBWP to a DL BWP other than the default DL BWP. The UE may restart thetimer to the initial value when it successfully decodes a DCI toschedule PDSCH(s) in its active DL BWP. The UE may switch its active DLBWP to the default DL BWP when the BWP timer expires.

In an example embodiment, a UE configured for operation in bandwidthparts (BWPs) of a serving cell, may be configured by higher layers forthe serving cell a set of bandwidth parts (BWPs) for receptions by theUE (DL BWP set) or a set of BWPs for transmissions by the UE (UL BWPset). In an example, for a DL BWP or UL BWP in a set of DL BWPs or ULBWPs, respectively, the UE may be configured at least one of followingfor the serving cell: a subcarrier spacing for DL and/or UL provided byhigher layer parameter, a cyclic prefix for DL and/or UL provided byhigher layer parameter, a number of contiguous PRBs for DL and/or ULprovided by higher layer parameter, an offset of the first PRB for DLand/or UL in the number of contiguous PRBs relative to the first PRB byhigher layer, or Q control resource sets if the BWP is a DL BWP.

In an example embodiment, for each serving cell, higher layer signallingmay configure a UE with Q control resource sets. In an example, forcontrol resource set q, 0≤q<Q, the configuration may comprise at leastone of following: a first OFDM symbol provided by one or more higherlayer parameters, a number of consecutive OFDM symbols provided by oneor more higher layer parameters, a set of resource blocks provided byone or more higher layer parameters, a CCE-to-REG mapping provided byone or more higher layer parameters, a REG bundle size, in case ofinterleaved CCE-to-REG mapping, provided by one or more higher layerparameters, or antenna port quasi-collocation provided by higher layerparameter.

In an example embodiment, a control resource set may comprise a set ofCCEs numbered from 0 to N_(CCE,q)−1 where N_(CCE,q) may be the number ofCCEs in control resource set q.

In an example embodiment, the sets of PDCCH candidates that a UEmonitors may be defined in terms of PDCCH UE-specific search spaces. APDCCH UE-specific search space at CCE aggregation level L∈{1, 2, 4, 8}may be defined by a set of PDCCH candidates for CCE aggregation level L.In an example, for a DCI format, a UE may be configured per serving cellby one or more higher layer parameters a number of PDCCH candidates perCCE aggregation level L.

In an example embodiment, in non-DRX mode operation, a UE may monitorone or more PDCCH candidate in control resource set q according to aperiodicity of W_(PDCCH, q) symbols that may be configured by one ormore higher layer parameters for control resource set q.

In an example embodiment, if a UE is configured with higher layerparameter, e.g., cif-InSchedulingCell, the carrier indicator field valuemay correspond to cif-InSchedulingCell.

In an example embodiment, for the serving cell on which a UE may monitorone or more PDCCH candidate in a UE-specific search space, if the UE isnot configured with a carrier indicator field, the UE may monitor theone or more PDCCH candidates without carrier indicator field. In anexample, for the serving cell on which a UE may monitor one or morePDCCH candidates in a UE-specific search space, if a UE is configuredwith a carrier indicator field, the UE may monitor the one or more PDCCHcandidates with carrier indicator field.

In an example embodiment, a UE may not monitor one or more PDCCHcandidates on a secondary cell if the UE is configured to monitor one ormore PDCCH candidates with carrier indicator field corresponding to thatsecondary cell in another serving cell. For example, for the servingcell on which the UE may monitor one or more PDCCH candidates, the UEmay monitor the one or more PDCCH candidates at least for the sameserving cell.

In an example embodiment, a UE may receive PDCCH and PDSCH in a DL BWPaccording to a configured subcarrier spacing and CP length for the DLBWP. A UE may transmit PUCCH and PUSCH in an UL BWP according to aconfigured subcarrier spacing and CP length for the UL BWP.

In an example embodiment, a UE may be configured, by one or more higherlayer parameters, a DL BWP from a configured DL BWP set for DLreceptions. A UE may be configured by one or more higher layerparameters, an UL BWP from a configured UL BWP set for UL transmissions.If a DL BWP index field is configured in a DCI format scheduling PDSCHreception to a UE, the DL BWP index field value may indicate the DL BWP,from the configured DL BWP set, for DL receptions. If an UL-BWP indexfield is configured in a DCI format scheduling PUSCH transmission from aUE, the UL-BWP index field value may indicate the UL BWP, from theconfigured UL BWP set, for UL transmissions.

In an example embodiment, for TDD, a UE may expect that the centerfrequency for the DL BWP is same as the center frequency for the UL BWP.

In an example embodiment, a UE may not monitor PDCCH when the UEperforms measurements over a bandwidth that is not within the DL BWP forthe UE.

In an example embodiment, for an initial active DL BWP, UE may identifythe bandwidth and frequency of the initial active DL BWP in response toreceiving the NR-PBCH.

In an example embodiment, a bandwidth of an initial active DL BWP may beconfined within the UE minimum bandwidth for the given frequency band.For example, for flexible for DL information scheduling, the bandwidthmay be indicated in PBCH, and/or some bandwidth candidates may bepredefined. For example, x bits may be employed for indication. Thisenables.

In an example embodiment, a frequency location of initial active DL BWPmay be derived from the bandwidth and SS block, e.g. center frequency ofthe initial active DL BWP. For example, a SS block may have a frequencyoffset, as the edge of SS block PRB and data PRB boundary may not bealigned. Predefining the frequency location of SS block and initialactive DL BWP may reduce the PBCH payload size, additional bits are notneeded for indication of frequency location of initial active DL BWP.

In an example, for the paired UL BWP, the bandwidth and frequencylocation may be informed in RMSI.

In an example embodiment, for a UE, gNB may configure a set of BWPs byRRC. The UE may transmit or receive in an active BWP from the configuredBWPs in a given time instance. For example, an activation/deactivationof DL bandwidth part by means of timer for a UE to switch its active DLbandwidth part to a default DL bandwidth part may be supported. In thiscase, when the timer at the UE side expires, e.g. the UE has notreceived scheduling DCI for X ms, the UE may switch to the default DLBWP.

In an example, a new timer, e.g., BWPDeactivationTimer, may be definedto deactivate the original BWP and switch to the default BWP. TheBWPDeactivationTimer may be started when the original BWP is activatedby the activation/deactivation DCI. If PDCCH on the original BWP isreceived, a UE may restart the BWPDeactivationTimer associated with theoriginal BWP. For example, if the BWPDeactivationTimer expires, a UE maydeactivate the original BWP and switch to the default BWP, may stop theBWPDeactivationTimer for the original BWP, and may (or may not) flushall HARQ buffers associated with the original BWP.

In an example embodiment, gNB and UE may have different understanding ofthe starting of the timer since the UE may miss scheduling grants. In anexample, the UE may be triggered to switch to the default BWP, but gNBmay schedules the UE in the previous active BWP. For example, in thecase that the default BWP is nested within other BWPs, gNB may restrictthe location of the CORESET of BWP2 to be within BWP1 (e.g., the narrowband BWP1 may be the default BWP). Then the UE may receive CORESET andswitch back to BWP2 if it mistakenly switches to the default BWP.

In an example embodiment, for a case that the default BWP and the otherBWPs are not overlapped in frequency domain, it may not solve a missswitching problem by restricting the location of the CORESET. Forexample, the gNB may maintain a timer for a UE. When the timer expires,e.g. there is no data scheduling for the UE for Y ms, or gNB has notreceived feedback from the UE for Y′ ms, the UE may switch to thedefault BWP to send paging signal or re-schedule the UE in the defaultBWP.

In an example embodiment, gNB may not fix the default bandwidth part tobe the same as initial active bandwidth part it. Since the initialactive DL BWP may be the SS block bandwidth which is common to UEs inthe cell, the traffic load may be very heavy if many UEs fall back tosuch small bandwidth for data transmission. Configuring the UEs withdifferent default BWPs may help to balance the load in the systembandwidth.

In an example embodiment, on a Scell, there may be no initial active BWPsince the initial access is performed on the Pcell. For example, theinitially activated DL BWP and/or UL BWP when the Scell is activated maybe configured or reconfigured by RRC signaling. In an example, thedefault BWP of the Scell may also be configured or reconfigured by RRCsignaling. To strive for a unified design for both Pcell and Scell, thedefault BWP may be configured or reconfigured by the RRC signalling, andthe default BWP may be one of the configured BWPs of the UE.

In an example embodiment, gNB may configure UE-specific default DL BWPother than initial active BWP after RRC connection, e.g., for thepurpose of load balancing. The default BWP may support other connectedmode operations (besides operations supported by initial active BWP) forexample fall back and connected mode paging. In this case, the defaultBWP may comprise common search space, at least the search space neededfor monitoring the pre-emption indications. For example, for FDD, thedefault DL and UL BWPs may be independently configured to the UE.

In an example, the initial active DL/UL BWP may be set as default DL/ULBWP. In an example, a UE may return to default DL/UL BWP in some cases.For example, if a UE does not receive control for a long time, the UEmay fallback to default BWP.

In an example embodiment, gNB may configure UE with multiple BWPs. Forexample, the multiple BWPs may share at least one CORESET includingdefault BWP. For example, CORESET for RMSI may be shared for allconfigured BWP. Without going back to another BWP or default BWP, the UEmay receive control information via the common CORESET. To minimize theambiguity of resource allocation, the common CORESET may schedule datawithin only default BWP. For example, frequency region of default BWPmay belong to all the configured BWPs.

In an example embodiment, when the configured BWP is associated with adifferent numerology from default BWP, a semi-static pattern of BWPswitching to default BWP may be considered. For example, to check RMSIat least periodically, switching to default BWP may be considered. Thismay be necessary particularly when BWPs use different numerologies.

In an example embodiment, in terms of reconfiguration of default BWPfrom initial BWP, it may be considered for RRC connected UEs. ForRRC_IDLE UEs, default BWP may be same as initial BWP (or, RRC_IDLE UEmay fallback to initial BWP regardless of default BWP). If a UE performsmeasurement based on SS block, reconfiguration of default BWP outside ofinitial BWP may become very inefficient due to frequent measurement gap.In this sense, if default BWP is reconfigured to outside of initial BWP,the following conditions may be satisfied: a UE is in CONNECTED mode,and a UE is not configured with SS block based measurement for bothserving cell and neighbor cells.

In an example embodiment, a DL BWP other than the initial active DL BWPmay be configured to a UE as the default DL BWP. The reconfiguring thedefault DL BWP may be due to load balancing and/or differentnumerologies employed for active DL BWP and initial active DL BWP.

In an example embodiment, a default BWP on Pcell may be an initialactive DL BWP for transmission of RMSI, comprising RMSI CORESET withCSS. The RMSI CORESET may comprise USS. The initial active/default BWPmay remain active BWP for the user also after UE becomes RRC connected.

In an example embodiment, for a paired spectrum, downlink and uplinkbandwidth parts may be independently activated while, for an unpairedspectrum downlink and uplink bandwidth parts are jointly activated. Incase of bandwidth adaptation, where the bandwidth of the active downlinkBWP may be changed, there may, in case of an unpaired spectrum, be ajoint activation of a new downlink BWP and new uplink BWP. For example,a new DL/UL BWP pair where the bandwidth of the uplink BWPs may be thesame (e.g., no change of uplink BWP).

In an example embodiment, there may be an association of DL BWP and ULBWP in RRC configuration. For example, in case of TDD, a UE may notretune the center frequency of channel BW between DL and UL. In thiscase, since the RF is shared between DL and UL in TDD, a UE may notretune the RF BW for every alternating DL-to-UL and UL-to-DL switching.

In an example embodiment, making an association between DL BWP and ULBWP may allow that one activation/deactivation command may switch bothDL and UL BWPs at once. Otherwise, separate BWP switching commands maybe necessary.

In an example embodiment, a DL BWP and an UL BWP may be configured tothe UE separately. Pairing of the DL BWP and the UL BWP may imposeconstrains on the configured BWPs, e.g., the paired DL BWP and UL BWPmay be activated simultaneously. For example, gNB may indicate a DL BWPand an UL BWP to a UE for activation in a FDD system. In an example, gNBmay indicate a DL BWP and an UL BWP with the same center frequency to aUE for activation in a TDD system. Since the activation/deactivation ofthe BWP of the UE is instructed by gNB, no paring or association of theDL BWP and UL BWP may be mandatory even for TDD system. It may be up togNB implementation.

In an example embodiment, the association between DL carrier and ULcarrier within a serving cell may be done by carrier association. Forexample, for TDD system, UE may not be expected to retune the centerfrequency of channel BW between DL and UL. To achieve it, an associationbetween DL BWP and UL BWP may be needed. For example, a way to associatethem may be to group DL BWP configurations with same center frequency asone set of DL BWPs and group UL BWP configurations with same centerfrequency as one set of UL BWPs. The set of DL BWPs may be associatedwith the set of UL BWPs sharing the same center frequency.

For an FDD serving cell, there may be no association between DL BWP andUL BWP if the association between DL carrier and UL carrier within aserving cell may be done by carrier association.

In an example embodiment, UE may identify a BWP identity from DCI tosimplify the indication process. The total number of bits for BWPidentity may depend on the number of bits that may be employed withinthe scheduling DCI (or switching DCI) and the UE minimum BW. The numberof BWPs may be determined by the UE supported minimum BW along with thenetwork maximum BW. For instance, in a similar way, the maximum numberof BWP may be determined by the network maximum BW and the UE minimumBW. In an example, if 400 MHz is the network maximum BW and 50 MHz isthe UE minimum BW, 8 BWP may be configured to the UE which means that 3bits may be needed within the DCI to indicate the BWP. In an example,such a split of the network BW depending on the UE minimum BW may beuseful for creating one or more default BWPs from the network side bydistributing UEs across the entire network BW, e.g., load balancingpurpose.

In an example embodiment, at least 2 DL and 2 UL BWP may be supported bya UE for a BWP adaption. For example, the total number of BWP supportedby a UE may be given by 2≤Number of DL/UL BWP≤floor (Network maximumBW/UE minimum DL/UL BW). For example, a maximum number of configuredBWPs may be 4 for DL and UL respectively. For example, a maximum numberof configured BWPs for UL may be 2.

In an example embodiment, different sets of BWPs may be configured fordifferent DCI formats/scheduling types respectively. For example, somelarger BWPs may be configured for non-slot-based scheduling than thatfor slot-based scheduling. If different DCI formats are defined forslot-based scheduling and non-slot-based scheduling, different BWPs maybe configured for different DCI formats. This may provide flexibilitybetween different scheduling types without increasing DCI overhead. The2-bit bitfield may be employed to indicate a BWP among the four for theDCI format. For example, 4 DL BWPs or [2 or 4] UL BWPs may be configuredfor each DCI formats. Same or different BWPs may be configured fordifferent DCI formats.

In an example embodiment, a required maximum number of configured BWPs(may be not comprising the initial BWP) may depend on the flexibilityneeded for a BWP functionality. For example, in the minimal case ofsupporting bandlimited devices, it may be sufficient to be able toconfigure one DL BWP and one UL BWP (or a single DL/UL BWP pair in caseof unpaired spectrum). For example, to support bandwidth adaptation,there may be a need to configure (at least) two DL BWPs and a singleuplink BWP for paired spectrum (or two DL/UL BWP pairs for unpairedspectrum). For example, to support dynamic load-balancing betweendifferent parts of the spectrum, there may be a need to configure one ormore DL (UL) BWPs that jointly cover different parts of the downlink(uplink) carrier. In an example, for dynamic load balancing, it may besufficient with two bandwidth parts. In addition to the two bandwidthparts, two additional bandwidth parts may be needed for bandwidthadaptation. For example, a Maximum number of configured BWPs may be fourDL BWPs and two UL BWPs for a paired spectrum. For example, a Maximumnumber of configured BWPs may be four DL/UL BWP pairs for an unpairedspectrum.

In an example embodiment, UE may monitor for RMSI and broadcast OSIwhich may be transmitted by the gNB within the common search space (CSS)on the PCell. In an example, RACH response and paging control monitoringon the PCell may be transmitted within the CSS. In an example, when a UEis allowed to be on an active BWP configured with UE-specific searchspace (USSS or USS), the UE may not monitor the common search space.

In an example, for a PCell, at least one of configured DL bandwidthparts may comprise at least one CORESET with a CSS type. For example, tomonitor RMSI and broadcast OSI, UE may periodically switch to the BWPcontaining the CSS. In an example, the UE may periodically switch to theBWP containing the CSS for RACH response and paging control monitoringon the PCell.

In an example, if BWP switching to monitor the CSS happens frequently,it may result in increasing overhead. In an example, the overhead due tothe CSS monitoring may depends on overlapping in frequency between anytwo BWPs. In an example, in a nested BWP configuration where one BWP isa subset of another BWP, the same CORESET configuration may be employedacross the BWPs. In this case, unless reconfigured otherwise, a defaultBWP may be the one containing the CSS, and another BWP may contain theCSS. In an example, the BWPs may be partially overlapping. If theoverlapping region is sufficient, a CSS may be across a first BWP and asecond BWP. In an example, two non-overlapping BWP configurations mayexist.

In an example embodiment, there may be one or more benefits ofconfiguring the same CORESET containing the CSS across BWPs. Forexample, RMSI and broadcast OSI monitoring may be handled withoutnecessitating BWP switching. In an example, RACH response and pagingcontrol monitoring on the PCell may also be handled without switching.For example, if CORESET configuration is the same across BWPs,robustness for BWP switching may improve, because even if gNB and UE areout-of-sync as to which BWP is currently active, the DL control channelmay work. In an example, one or more constraints on BWP configurationmay not be too much, considering that BWP may be for power saving, eventhe nested configuration may be very versatile for differentapplications.

In an example embodiment, for the case where the BWP configurations arenon-overlapping in frequency, there may not be spec mandate for UE tomonitor RMSI and broadcast OSI in the CSS. It may be left toimplementation to handle this case.

In an example embodiment, NR may support group-common search space(GCSS). For example, the GCSS may be employed as an alternative to CSSfor certain information. In an example, gNB may configure GCSS within aBWP for a UE, and information such as RACH response and paging controlmay be transmitted on GCSS. For example, the UE may monitor GCSS insteadof switching to the BWP containing the CSS for such information.

In an example embodiment, for pre-emption indication and othergroup-based commands on a serving cell, gNB may transmit the informationon GCSS. UE may monitor the GCSS for the information. For example, forSCell which may not have CSS.

In an example embodiment, NR may configure a CORESET without using aBWP. For example, NR support to configure a CORESET based on a BWP toreduce signaling overhead. In an example, a first CORESET for a UEduring an initial access may be configured based on its default BWP. Inan example, a CORESET for monitoring PDCCH for RAR and paging may beconfigured based on a DL BWP. In an example, the CORESET for monitoringgroup common (GC)-PDCCH for SFI may be configured based on a DL BWP. Inan example, the CORESET for monitoring GC-DCI for pre-emption indicationmay be configured based on a DL BWP. In an example, the BWP index may beindicated in the CORESET configuration. In an example, the default BWPindex may not be indicated in the CORESET configuration.

In an example embodiment, the contention-based random access (CBRA) RACHprocedure may be supported via an initial active DL and UL BWPs sincethe UE identity is unknown to the gNB. In an example, thecontention-free random access (CFRA) RACH procedure may be supported viathe USS configured in an active DL BWP for the UE. For example, in thiscase, an additional CSS for RACH purpose may not need to be configuredper BWP. For example, idle mode paging may be supported via an initialactive DL BWP and the connected mode paging may be supported via adefault BWP. No additional configurations for the BWP for pagingpurposes may not be needed for paging. For the case of pre-emption, aconfigured BWP (on a serving cell) may have the CSS configured formonitoring the pre-emption indications.

In an example embodiment, for a configured DL BWP, a group-common searchspace may be associated with at least one CORESET configured for thesame DL BWP. For example, depending on the monitoring periodicity ofdifferent group-common control information types, it may not bepractical for the UE to autonomously switch to a default BWP where agroup-common search space is available to monitor for such DCI. In thiscase, if there is at least one CORESET configured on a DL BWP, it may bepossible to configure a group-common search space in the same CORESET.

In an example embodiment, a center frequency of the activated DL BWP maynot be changed. In an example, the center frequency of the activated DLBWP may be changed. For example, For TDD, if the center frequency of theactivated DL BWP and deactivated DL BWP is not aligned, the active ULBWP may be switched implicitly.

In an example embodiment, BWPs with different numerologies may beoverlapped, and rate matching for CSI-RS/SRS of another BWP in theoverlapped region may be employed to achieve dynamic resource allocationof different numerologies in FDM/TDM fashion. In an example, for the CSImeasurement within one BWP, if the CSI-RS/SRS is collided with data/RSin another BWP, the collision region in another BWP may be rate matched.For example, CSI information over the two BWPs may be known at a gNBside by UE reporting. Dynamic resource allocation with differentnumerologies in a FDM manner may be achieved by gNB scheduling.

In an example embodiment, PUCCH resources may be configured in aconfigured UL BWP, in a default UL BWP and/or in both. For instance, ifthe PUCCH resources are configured in the default UL BWP, UE may retuneto the default UL BWP for transmitting an SR. for example, the PUCCHresources are configured per BWP or a BWP other than the default BWP,the UE may transmit an SR in the current active BWP without retuning.

In an example embodiment, if a configured SCell is activated for a UE, aDL BWP may be associated with an UL BWP at least for the purpose ofPUCCH transmission, and a default DL BWP may be activated. If the UE isconfigured for UL transmission in same serving cell, a default UL BWPmay be activated.

In an example embodiment, at least one of configured DL BWPs comprisesone CORESET with common search space (CSS) at least in primary componentcarrier. The CSS may be needed at least for RACH response (msg2) andpre-emption indication.

In an example, for the case of no periodic gap for RACH responsemonitoring on Pcell, for Pcell, one of configured DL bandwidth parts maycomprise one CORESET with the CSS type for RMSI & OSI. For Pcell, aconfigured DL bandwidth part may comprise one CORESET with the CSS typefor RACH response & paging control for system information update. For aserving cell, a configured DL bandwidth part may comprise one CORESETwith the CSS type for pre-emption indication and other group-basedcommands.

In an example, for the case of a presence of periodic gap for RACHresponse monitoring on Pcell, for Pcell, one of configured DL bandwidthparts may comprise one CORESET with CSS type for RMSI, OSI, RACHresponse & paging control for system information update. For a servingcell, a configured DL bandwidth part may comprise one CORESET with theCSS type for pre-emption indication and other group-based commands.

In an example embodiment, BWPs may be configured with respect to commonreference point (PRB 0) on a NW carrier. In an example, the BWPs may beconfigured using TYPE1 RA as a set of contiguous PRBs, with PRBgranularity for the START and LENGTH, and the minimum length may bedetermined by the minimum supported size of a CORESET.

In an example embodiment, a CSS may be configured on a non-initial BWPfor RAR and paging.

In an example embodiment, to monitor (group) common channel for RRCCONNECTED UE, an initial DL BWP may comprise control channel for RMSI,OSI and paging and UE switches BWP to monitor such channel. In anexample, a configured DL BWP may comprise control channel for Msg2. Inan example, a configured DL BWP may comprise control channel for SFI. Inan example, a configured DL BWP may comprise pre-emption indication andother group common indicators like power control.

In an example embodiment, a DCI may explicitly indicateactivation/deactivation of BWP.

For example, a DCI without data assignment may comprise an indication toactivate/deactivate BWP. In an example, UE may receive a firstindication via a first DCI to activate/deactivate BWP. In order for theUE to start receiving data, a second DCI with a data assignment may betransmitted by the gNB. A UE may receive the first DCI in a targetCORESET in a target BWP. In an example, until there is CSI feedbackprovided to a gNB, the gNB scheduler may make conservative schedulingdecisions.

In an example, a DCI without scheduling for active BWP switching may betransmitted to measure the CSI before scheduling. It may be taken as animplementation issue of DCI with scheduling, for example, the resourceallocation field may be set to zero, which means no data may bescheduled. Other fields in this DCI may comprise one or more CSI/SRSrequest fields.

In an example embodiment, support for a single scheduling DCI to triggeractive BWP switching may be motivated by dynamic BWP adaptation for UEpower saving during active state (which may comprise ON duration andwhen inactivity timer is running when C-DRX is configured). For example,with a C-DRX enabled, a UE may consume significant amount of powermonitoring PDCCH without decoding any grant. To reduce the powerconsumption during PDCCH monitoring, two BWPs may be configured: anarrower BWP for PDCCH monitoring, and a wider BWP for scheduled data.In such a case, the UE may switch back-and-forth between the narrowerBWP and the wider BWP, depending on the burstiness of the traffic. Forexample, the UE may be revisiting a BWP that it has dwelled onpreviously. For this case, combining a BWP switching indication and ascheduling grant may result in low latency and reduced signallingoverhead for BWP switching.

In an example embodiment, a SCell activation and deactivation maytrigger the corresponding action for its configured BWP. In an example,a SCell activation and deactivation may not trigger the correspondingaction for its configured BWP.

In an example embodiment, a dedicated BWP activation/deactivation DCImay impact a DCI format. For example, a scheduling DCI with a dummygrant may be employed. the dummy grant may be constructed byinvalidating one or some of the fields, for example, the resourceallocation field. In an example, it may be feasible to leverage afallback scheduling DCI format (which contains a smaller payload) toimprove the robustness for BWP DCI signalling, without incurring extrawork on introducing a new DCI format.

In an example embodiment, a DCI with data assignment may comprise anindication to activate/deactivate BWP along with a data assignment. Forexample, a UE may receive a combined data allocation and BWPactivation/deactivation message. For example, a DCI format may comprisea field to indicate BWP activation/deactivation along with a fieldindicating UL/DL grant. In this case, the UE may start receiving datawith a single DCI. In this case, the DCI may need indicate one or moretarget resources of a target BWP. A gNB scheduler may have littleknowledge of the CSI in the target BW and may have to make conservativescheduling decisions.

In an example embodiment, for the DCI with data assignment, the DCI maybe transmitted on a current active BWP and scheduling information may befor a new BWP. For example, there may be a single active BWP. There maybe one DCI in a slot for scheduling the current BWP or schedulinganother BWP. The same CORESET may be employed for the DCI scheduling thecurrent BWP and the DCI scheduling another BWP. For example, to reducethe number of blind decoding, the DCI payload size for the DCIscheduling current BWP and the scheduling DCI for BWP switching may bethe same.

In an example embodiment, to support the scheduling DCI for BWPswitching, a BWP group may be configured by gNB, in which a numerologyin one group may be the same. In an example, the BWP switching for theBWP group may be configured, in which BIF may be present in the CORESETsfor one or more BWPs in the group. For example, scheduling DCI for BWPswitching may be configured per BWP group, in which an active BWP in thegroup may be switched to any other BWP in the group.

In an example, embodiment, a DCI comprising scheduling assignment/grantmay not comprise active-BWP indicator. For a paired spectrum, ascheduling DCI may switch UEs active BWP for the transmission directionthat the scheduling is valid for. For an unpaired spectrum, a schedulingDCI may switch the UEs active DL/UL BWP pair regardless of thetransmission direction that the scheduling is valid for. There may be apossibility for downlink scheduling assignment/grant with “zero”assignment, in practice allowing for switch of active BWP withoutscheduling downlink or uplink transmission

In an example embodiment, a timer-based activation/deactivation BWP maybe supported. For example, a timer for activation/deactivation of DL BWPmay reduce signaling overhead and may enable UE power savings. Theactivation/deactivation of a DL BWP may be based on an inactivity timer(referred to as a BWP inactive (or inactivity) timer). For example, a UEmay start and reset a timer upon reception of a DCI. When the UE is notscheduled for the duration of the timer, the timer may expire. In thiscase, the UE may activate/deactivate the appropriate BWP in response tothe expiry of the timer. For example, the UE may activate for examplethe Default BWP and may deactivate the source BWP.

For example, a BWP inactivity timer may be beneficial for power savingfor a UE switching to a default BWP with smaller BW and fallback for aUE missing DCI based activation/deactivation signaling to switch fromone BWP to another BWP.

In an example embodiment, triggering conditions of the BWP inactivitytimer may follow the ones for the DRX timer in LTE. For example, anOn-duration of the BWP inactivity timer may be configured and the timermay start when a UE-specific PDCCH is successfully decoded indicating anew transmission during the On-duration. The timer may restart when aUE-specific PDCCH is successfully decoded indicating a new transmission.The timer may stop once the UE is scheduled to switch to the default DLBWP.

In an example embodiment, for fallback, the BWP inactivity timer maystart once the UE switches to a new DL BWP. The timer may restart when aUE-specific PDCCH is successfully decoded, wherein the UE-specific PDCCHmay be associated with a new transmission, a retransmission or someother purpose, e.g., SPS activation/deactivation if supported.

In an example embodiment, a UE may switch to a default BWP if the UEdoes not receive any control/data from the network during a BWPinactivity timer running. The timer may be reset upon reception of anycontrol/data. For example, the timer may be triggered when UE receives aDCI to switch its active DL BWP from the default BWP to another. Forexample, the timer may be reset when a UE receives a DCI to schedulePDSCH(s) in the BWP other than the default BWP.

In an example embodiment, a BWP inactivity-timer may enable thefall-back to default BWP on Pcell and Scell.

In an example embodiment, a timer-based activation/deactivation of BWPmay be similar to a UE DRX timer. For example, there may not be aseparate inactivity timer for BWP activation/deactivation for the UE DRXtimer. For example, one of the UE DRX inactivity timer may trigger BWPactivation/deactivation.

For example, there may be a separate BWP inactivity timer from the UEDRX timer. For example, the DRX timers may be defined in a MAC layer,and the BWP inactivity timer may be defined in a physical layer. In anexample, If the same DRX inactivity timer is employed for BWPactivation/deactivation, UE may stay in a wider BWP for as long as theinactivity timer is running, which may be a long time. For example, theDRX inactivity timer may be set to a large value of 100-200 millisecondsfor C-DRX cycle of 320 milliseconds, larger than the ON duration (10milliseconds). This may imply that power saving due to narrower BWP maynot be achievable. To realize potential of UE power saving promised byBWP switching, a new timer may be defined, and it may be configured tobe smaller than the DRX inactivity timer. From the point of view of DRXoperation, BWP switching may allow UE to operate at different powerlevels during the active state, effectively providing some moreintermediate operating points between the ON and OFF states.

In an example embodiment, with a DCI explicit activation/deactivation ofBWP, a UE and a gNB may not be synchronized with respect to which BWP isactivated/deactivated. The gNB scheduler may not have CSI informationrelated to a target BWP for channel-sensitive scheduling. The gNB may belimited to conservative scheduling for one or more first severalscheduling occasions. The gNB may rely on periodic or aperiodic CSI-RSand associated CQI report to perform channel-sensitive scheduling.Relying on periodic or aperiodic CSI-RS and associated CQI report maydelay channel-sensitive scheduling and/or lead to signaling overhead(e.g. in the case where we request aperiodic CQI). To mitigate a delayin acquiring synchronization and channel state information, a UE maytransmit an acknowledgement upon receiving an activation/deactivation ofBWP. For example, a CSI report based on the provided CSI-RS resource maybe transmitted after activation of a BWP and is employed asacknowledgment of activation/deactivation.

In an example embodiment, a gNB may provide a sounding reference signalfor a target BWP after a UE tunes to a new bandwidth. In an example, theUE may report the CSI, which is employed as an acknowledgement by thegNB to confirm that the UE receive an explicit DCI command andactivates/deactivates the appropriate BWPs. In an example, for the caseof an explicit activation/deactivation via DCI with data assignment, afirst data assignment may be carried out without a CSI for the targetBWP

In an example embodiment, a guard period may be defined to take RFretuning and the related operations into account. For example, a UE mayneither transmit nor receive signals in the guard period. A gNB may needto know the length of the guard period. For example, the length of theguard period may be reported to the gNB as a UE capability. The lengthof the guard period may be closely related on the numerologies of theBWPs and the length of the slot. For example, the length of the guardperiod for RF retuning may be reported as a UE capability. In anexample, the UE may report the absolute time in μs. in an example, theUE may report the guard period in symbols.

In an example embodiment, after the gNB knows the length of the guardperiod by UE reporting, the gNB may want to keep the time domainposition of guard period aligned between the gNB and the UE. Forexample, the guard period for RF retuning may be predefined for timepattern triggered BWP switching. In an example, for the BWP switchingtriggered by DCI and timer, the guard period for DCI and timer based BWPswitching may be an implementation issue. In an example, for BWPswitching following some time pattern, the position of the guard periodmay be defined. For example, if the UE is configured to switchperiodically to a default BWP for CSS monitoring, the guard period maynot affect the symbols carrying CSS.

In an example embodiment, a single DCI may switch the UE's active BWPform one to another (of the same link direction) within a given servingcell. A separate field may be employed in the scheduling DCI to indicatethe index of the BWP for activation, such that UE may determine thecurrent DL/UL BWP according to a detected DL/UL grant without requiringany other control information. In case the BWP change does not happenduring a certain time duration, the multiple scheduling DCIs transmittedin this duration may comprise the indication to the same BWP. During thetransit time when potential ambiguity may happen, gNB may sendscheduling grants in the current BWP or together in the other BWPscontaining the same target BWP index, such that UE may obtain the targetBWP index by detecting the scheduling DCI in either one of the BWPs. Theduplicated scheduling DCI may be transmitted K times. When UE receiveone of the K times transmissions, UE may switch to the target BWP andstart to receive or transmit (UL) in the target BWP according to the BWPindication field.

In an example embodiment, switching between BWPs may not introduce largetime gaps when UE may not be able to receive due to re-tuning, neitherafter detecting short inactivity (Case 1) or when data activity isreactivated (Case 2). For example, in Case 2, long breaks of severalslots may severely impact the TCP ramp up as UE may not be able totransmit and receive during those slots, impacting obtained RTT and datarate. Case 1 may be seen less problematic at first glance but similarlylong break in reception may make UE out of reach from network point ofview reducing network interest to utilize short inactivity timer.

In an example, if BWP switching takes significant time, and UE requiresnew reference symbols to update AGC, channel estimation etc., the systemmay have less possibilities/motivation to utilize active BWP adaption inthe UE. This may be achieved by preferring configuration where BWPcenter frequency remains the same when switching between BWPs.

In an example embodiment, a frequency location of UE RF bandwidth may beindicated by gNB. For example, considering the UE RF bandwidthcapability, the RF bandwidth of the UE may be usually smaller than thecarrier bandwidth. The supported RF bandwidth for a UE is usually a setof discrete values (e.g., 10 MHz, 20 MHz, 50 MHz and so on), for energysaving purpose, the UE RF bandwidth may be determined as the minimumavailable bandwidth supporting the BWP bandwidth. But the granularity ofBWP bandwidth is PRB level, which is decoupled with UE RF bandwidth andmore flexible. As a result, in most cases the UE RF bandwidth is largerthan the BWP bandwidth. The UE may receive the signal outside thecarrier bandwidth, especially if the configured BWP is configured nearthe edge of the carrier bandwidth, as shown in FIG. 4(a). And theinter-system interference or the interference from the adjacent celloutside the carrier bandwidth may impact the receiving performance ofthe BWP. Thus, to keep the UE RF bandwidth in the carrier bandwidth asshown in FIG. 4(b), it is necessary to indicate the frequency locationof the UE RF bandwidth by gNB.

In an example embodiment, in terms of measurement gap configuration, thegap duration may be determined based on the measurement duration andnecessary retuning gap. For example, different retuning gap may beneeded depending on the cases. For example, if a UE does not need toswitch its center, the retuning may be small such as 20 us. For the casethat the network may not know whether the UE needs to switch its centeror not to perform measurement, a UE may indicate the necessary retuninggap for a measurement configuration.

In an example embodiment, the necessary gap may depend on the currentactive BWP which may be dynamically switched via switching mechanism. Inthis case, for example, UEs may need to dynamically indicate thenecessary gap.

In an example embodiment, the measurement gap may be implicitly created,wherein the network may configure a certain gap (which may comprise thesmallest retuning latency, for example, the network may assume smallretuning gap is necessary if both measurement bandwidth and active BWPmay be included within UE maximum RF capability assuming centerfrequency of current active BWP is not changed). In this case, forexample, if a UE needs more gap than the configured, the UE may skipreceiving or transmitting.

In an example embodiment, different measurement gap and retuning latencymay be assumed for RRM and CSI respectively. For CSI measurement, ifperiodic CSI measurement outside of active BWP is configured, a UE mayneed to perform its measurement periodically per measurementconfiguration. For RRM, it may be up to UE implementation where toperform the measurement as long as it satisfies the measurementrequirements. In this case, for example, the worst-case retuning latencyfor a measurement may be employed. In an example, as the retuninglatency may be different between intra-band and inter-band retuning,separate measurement gap configuration between intra-band and inter-bandmeasurement may be considered.

In an example embodiment, for multiple DCI formats with the same DCIsize of a same RNTI, a respective DCI format may comprise an explicitidentifier to distinguish them. For example, a same DCI size may comefrom a few (but not a large number of) zero-padding bits at least inUE-specific search space.

In an example embodiment, when there is a BWP switching, a DCI in thecurrent BWP may need to indicate resource allocation in the next BWPthat the UE is expected to switch. For example, the resource allocationmay be based on the UE-specific PRB indexing, which may be per BWP. Arange of the PRB indices may change as the BWP changes. In an example,the DCI to be transmitted in current BWP may be based on the PRBindexing for the current BWP. The DCI may need to indicate the RA in thenew BWP, which may arouse a conflict. To resolve the conflict withoutsignificantly increasing UEs blind detection overhead, the DCI size andfields may not change per BWP for a given DCI type.

In an example embodiment, as the range of the PRB indices may change asthe BWP changes, one or more employed bits among the total field for RAmay be dependent on the employed BWP. For example, UE may employ theindicated BWP ID that the resource allocation is intended to identifythe resource allocation field.

In an example embodiment, a DCI size of the BWP may consider two cases.One case may be a normal DCI detection without BWP retuning, and theother case may be a DCI detection during the BWP retuning.

For example, in some cases, a DCI format may be independent of the BW ofthe active DL/UL BWP (which may be called as fallback DCI). In anexample, at least one of DCI formats for DL may be configured to havethe same size to a UE for one or more configured DL BWPs of a servingcell. In an example, at least one of the DCI formats for UL may beconfigured to have the same size to a UE for one or more configured ULBWPs of a serving cell. In an example embodiment, a BWP-dependent DCIformat may be monitored at the same time (which may be called as normalDCI) for both active DL BWP and active UL BWP. For example, UE may beconfigured to monitor both DCI formats at the same time. During the BWPactivation/deactivation, gNB may assign the fallback DCI format to avoidambiguity during the transition period.

In an example embodiment, if a UE is configured with multiple DL or ULBWPs in a serving cell, an inactive DL/UL BWP may be activated by a DCIscheduling a DL assignment or UL grant respectively in this BWP. As theUE is monitoring the PDCCH on the currently active DL BWP, the DCI maycomprise an indication to a target BWP that the UE may switch to forPDSCH reception or UL transmission. A BWP indication may be inserted inthe UE-specific DCI format for this purpose. The bit width of this fieldmay depend on either the maximum possible or presently configured numberof DL/UL BWPs. Similar to CIF, it may be simpler to set the BWPindication field to a fixed size based on the maximum number ofconfigured BWPs.

In an example, a DCI format size may match the BW of the BWP in whichthe PDCCH is received. To avoid an increase in the number of blinddecodes, the UE may identify the RA field based on the scheduled BWP.For example, for a transition from a small BWP to a larger BWP, the UEmay identify the RA field as being the LSBs of the required RA field forscheduling the larger BWP.

In an example embodiment, a same DCI size for scheduling different BWPsmay be defied by keeping a same size of resource allocation field forone or more configured BWPs. For example, gNB may not be aware ofwhether UE switches BWPs if gNB does not receive at least one responsefrom the UE (e.g., gNB may be aware of if UE switches BWPs based on areception of ACK/NACK from the UE). In an example, to avoid such amismatch between gNB and UE, NR may define fallback mechanism. Forexample, if there is no response from the UE, gNB may transmit thescheduling DCI for previous BWPs and that for newly activated BWP sincethe UE may receive the DCI on either BWP. When the gNB receives aresponse from the UE, the gNB may confirm that the active BWP switchingis completed. In an example, if a same DCI size for scheduling differentBWPs is considered and COREST configuration is also the same fordifferent BWPs, gNB may not transmit multiple DCIs.

In an example embodiment, DCI format(s) may be configureduser-specifically per cell, e.g., not per BWP. For example, after the UEsyncs to the new BWP, the UE may start to monitor pre-configuredsearch-space on the CORESET. If the DCI formats may be configured percell to keep the number of DCI formats, the corresponding header size inDCI may be small.

In an example embodiment, a size of DCI format in different BWPs mayvary and may change at least due to different size of RA bitmap ondifferent BWPs. For example, the size of DCI format configured in a cellfor a UE may be dependent on BWP it schedules.

In an example embodiment, the monitored DCI format size on asearch-space of a CORESET may be configurable with the sufficiently finegranularity (the granularity may be predefined). For example, themonitored DCI format size with sufficient granularity may be beneficialwhen a gNB may have the possibility to set freely the monitoring DCIformat size on a search-spaces of a CORESET, such that it mayaccommodate the largest actual DCI format size variant among one or moreBWPs configured in a serving cell.

In an example embodiment, for a UE-specific serving cell, one or more DLBWPs and one or more UL BWPs may be configured by dedicated RRC for aUE. For the case of PCell, this may be done as part of the RRCconnection establishment procedure. For the SCell, this may be done viaRRC configuration which may indicate the SCell parameters.

In an example embodiment, when a UE receives SCell activation command,there may be a default DL and/or UL BWP which may be activated sincethere may be at least one DL and/or UL BWP which may be monitored by theUE depending on the properties of the SCell (DL only or UL only orboth). This BWP which may be activated upon receiving SCell activationcommand, may be informed to the UE via the a RRC configuration whichconfigured the BWP on this serving cell.

For example, for SCell, RRC signalling for SCellconfiguration/reconfiguration may be employed to indicate which DL BWPand/or which UL BWP may be activated when the SCell activation commandis received by the UE. The indicated BWP may be the initially activeDL/UL BWP on the SCell. Therefore, SCell activation command may activateDL and/or UL BWP.

In an example embodiment, for a SCell, RRC signaling for the SCellconfiguration/reconfiguration may be employed for indicating a defaultDL BWP on the SCell which may be employed for fall back purposes. Forexample, the default DL BWP may be same or different from the initiallyactivated DL/UL BWP which is indicated to UE as part of the SCellconfiguration. In an example, a default UL BWP may be configured to UEfor the case of transmitting PUCCH for SR (as an example), in case thePUCCH resources are not configured in every BWP for the sake of SR.

In an example, a Scell may be for DL only. For the Scell for DL only, UEmay keep monitoring an initial DL BWP (initial active or default) untilUE receives SCell deactivation command.

In an example, a Scell may be for UL only. For the Scell for UL only,when UE receives a grant, UE may transmit on the indicated UL BWP. In anexample, the UE may not maintain an active UL BWP if UE does not receivea grant. In an example, not mainlining the active UL BWP due to no grantreceive may not deactivate the SCell.

In an example, a Scell may be for UL and DL. For the Scell for UL andDL, a UE may keep monitoring an initial DL BWP (initial active ordefault) until UE receives SCell deactivation command and. The UL BWPmay be employed when there is a relevant grant or an SR transmission.

In an example, a BWP deactivation may not result in a SCelldeactivation. For example, when the UE receives the SCell deactivationcommand, the active DL and/or UL BWPs may be considered deactivated.

In an example embodiment, if the SCell has its associated UL and/or a UEis expected to perform RACH procedure on SCell during activation,activation of UL BWP may be needed. For example, at SCell activation, DLonly (only active DL BWP) or DL/UL (both DL/UL active BWP) may beconfigured. Regarding SUL band as a SCell, a UE may select default ULBWP based on measurement or the network configures which one in itsactivation.

In an example embodiment, one or more BWPs are semi-staticallyconfigured via UE-specific RRC signaling. In a CA system, if a UEmaintains RRC connection with the primary component carrier (CC), theBWP in secondary CC may be configured via RRC signaling in the primaryCC.

In an example embodiment, one or more BWPs may be semi-staticallyconfigured to a UE via RRC signaling in PCell. A DCI transmitted inSCell may indicate a BWP among the one or more configured BWP, and grantdetailed resource based on the indicated BWP.

In an example embodiment, for a cross-CC scheduling, a DCI transmittedin PCell may indicate a BWP among the one or more configured BWPs, andgrants detailed resource based on the indicated BWP.

In an example embodiment, when a SCell is activated, a DL BWP may beinitially activated for configuring CORESET for monitoring the firstPDCCH in Scell. The DL BWP may serve as a default DL BWP in the SCell.In an example, since the UE performs initial access via a SS block inPCell, the default DL BWP in SCell may not be derived from SS block forinitial access. The default DL BWP in Scell may be configured by RRCsignaling in the PCell.

In an example embodiment, when an Scell is activated, an indicationindicating which DL BWP and/or which UL BWP are active may be in RRCsignalling for Scell configuration/reconfiguration. For example, the RRCsignalling for Scell configuration/reconfiguration may be employed forindicating which DL BWP and/or which UL BWP are initially activated whenthe Scell is activated.

In an example embodiment, when an Scell is activated, an indicationindicating which DL BWP and/or which UL BWP are active may be in Scellactivation signaling. For example, Scell activation signaling may beemployed for indicating which DL BWP and/or which UL BWP are initiallyactivated when the Scell is activated.

In an example embodiment, for PCells and pSCells, an initial defaultbandwidth parts for DL and UL (e.g., for RMSI reception and PRACHtransmission) may be valid until at least one bandwidth part isconfigured for the DL and UL via RRC UE-specific signaling,respectively, at what time the initial default DL/UL bandwidth parts maybecome invalid and new default DL/UL bandwidth parts may take effect. Inan example, for an Scell, the SCell configuration may comprise defaultDL/UL bandwidth parts

In an example embodiment, an initial BWP on Pcell may be defined by MIB.In an example, an initial BWP and default BWP may be separatelyconfigurable for the Scell. For an Scell if the Scell is activated, aninitial BWP may be the widest configured BWP of the Scell. For example,after the traffic burst is served, and an inactivity timer expires, a UEmay retune to default BWP which may be the narrow BWP, for powersavings, keeping the Scell active and may be ready to be opened brisklywhen additional data burst arrives.

In an example embodiment, a BWP on Scell may be activated by means ofcross-cell scheduling DCI, if cross-cell scheduling is configured to aUE. In this case, the gNB may activate a BWP on the Scell by indicatingCIF and BWPI in the scheduling DCI.

In an example embodiment, UE and/or gNB may perform synchronizationtracking within an active DL BWP without SS block. For example, TRSalong with DL BWP configuration may be configured. For example, a DL BWPwith SS block or TRS may be configured as a reference forsynchronization tracking, which may be similar to the design of CSSmonitoring when the BWP does not comprise a common CORESET.

In an example embodiment, SS-block based RRM measurements may bedecoupled with BWP framework. For example, measurement configurationsfor each RRM and CSI feedback may be independently configured frombandwidth part configurations. CSI and SRS measurements/transmissionsmay be performed within the BWP framework.

In an example embodiment, for a MCS assignment of the first one or moreDL data packets after active DL BWP switching, the network may assignrobust MCS to a UE for the first one or more DL data packets based onRRM measurement reporting. In an example, for a MCS assignment of thefirst one or more DL data packets after active DL BWP switching, thenetwork may signal to a UE by active DL BWP switching DCI to triggeraperiodic CSI measurement/reporting to speed up link adaptationconvergence. For a UE, periodic CSI measurement outside the active BWPin a serving cell may not supported. For a UE, RRM measurement outsideactive BWP in a serving cell may be supported. For a UE, RRM measurementoutside configured BWPs in a serving cell may be supported.

In an example embodiment, the RRM measurements may be performed on a SSBand/or CSI-RS. The RRM/RLM measurements may be independent of BWPs.

In an example embodiment, UE may not be configured with aperiodic CSIreports for non-active DL BWPs. For example, the CSI measurement may beobtained after the BW opening and the wide-band CQI of the previous BWPmay be employed as starting point for the other BWP on the NW carrier.

In an example embodiment, UE may perform CSI measurements on the BWPbefore scheduling. For example, before scheduling on a new BWP, the gNBmay intend to find the channel quality on the potential new BWPs beforescheduling the user on that BWP. In this case, the UE may switch to adifferent BWP and measure channel quality on the BWP and then transmitthe CSI report. There may be no scheduling needed for this case.

In an example embodiment, resource allocation for data transmission fora wireless device not capable of supporting the carrier bandwidth may bederived based on a two-step frequency-domain assignment process. In anexample, a first step may indicate a bandwidth part, and a second stepmay indicate one or more PRBs within the bandwidth part.

In an example embodiment, One or multiple bandwidth part configurationsfor each component carrier may be semi-statically signaled to a wirelessdevice. A bandwidth part may comprise a group of contiguous PRBs,wherein one or more reserved resources maybe be configured within thebandwidth part. The bandwidth of a bandwidth part may be equal to or besmaller than the maximal bandwidth capability supported by a wirelessdevice. The bandwidth of a bandwidth part may be at least as large asthe SS block bandwidth. The bandwidth part may or may not contain the SSblock. A Configuration of a bandwidth part may comprise at least one offollowing properties: Numerology, Frequency location (e.g. centerfrequency), or Bandwidth (e.g. number of PRBs).

In an example embodiment, a bandwidth part may be associated with one ormore numerologies, wherein the one or more numerologies may comprisesub-carrier spacing, CP type, or slot duration indication. In anexample, an wireless device may expect at least one DL bandwidth partand at least one UL bandwidth part being active among a set ofconfigured bandwidth parts for a given time instant. A wireless devicemay be assumed to receive/transmit within active DL/UL bandwidth part(s)using the associated numerology, for example, at least PDSCH and/orPDCCH for DL and PUCCH and/or PUSCH for UL, or combination thereof.

In an example, multiple bandwidth parts with same or differentnumerologies may be active for a wireless device simultaneously. Theactive multiple bandwidth parts may not imply that it is required forwireless device to support different numerologies at the same instance.The active DL/UL bandwidth part may not span a frequency range largerthan the DL/UL bandwidth capability of the wireless device in acomponent carrier.

In an example embodiment, NR may support single and multiple SS blocktransmissions in wideband CC in the frequency domain. For example, fornon-CA wireless device with a smaller BW capability and potentially forCA wireless device, NR may support a measurement gap for RRM measurementand potentially other purposes (e.g., path loss measurement for UL powercontrol) using SS block (if it is agreed that there is no SS block inthe active BW part(s)). wireless device may be informed of thepresence/parameters of the SS block(s) and parameters necessary for RRMmeasurement via at least one of following: RMSI, other systeminformation, and/or RRC signaling

In an example embodiment, a maximum bandwidth for CORESET for RMSIscheduling and NR-PDSCH carrying RMSI may be equal to or smaller than acertain DL bandwidth of NR that one or more wireless devices may supportin a frequency range. For example, at least for one RACH preambleformat, the bandwidth may be equal to or smaller than a certain ULbandwidth of NR that one or more wireless devices may support in afrequency range. There may be other RACH preamble format with largerbandwidth than a certain bandwidth of NR that one or more wirelessdevices may support.

In an example embodiment, CORESET for RMSI scheduling and NR-PDSCH forRMSI may be confined within the BW of one NR-PBCH. In an example,CORESET for RMSI scheduling is confined within the BW of one NR-PBCH andNR-PDSCH for RMSI may not be confined within the BW of one NR-PBCH. Inan example, CORESET for RMSI scheduling and NR-PDSCH for RMSI may not beconfined within the BW of one NR-PBCH.

In an example embodiment, there may be one active DL BWP for a giventime instant. For example, a configuration of a DL bandwidth part maycomprise at least one CORESET. PDSCH and corresponding PDCCH (PDCCHcarrying scheduling assignment for the PDSCH) may be transmitted withinthe same BWP if PDSCH transmission starts no later than K symbols afterthe end of the PDCCH transmission. In case of PDSCH transmissionstarting more than K symbols after the end of the corresponding PDCCH,PDCCH and PDSCH may be transmitted in different BWPs. The value of K maydepend on at least one of following numerology or possibly reportedwireless device retuning time. In an example, for the indication ofactive DL/UL bandwidth part(s) to a wireless device, DCI (explicitlyand/or implicitly), MAC CE, Time pattern (e.g. DRX like) and/orcombinations thereof may be considered.

In an example embodiment, NR may support switching between partial bandsfor SRS transmissions in a CC. For example, when an wireless device isnot capable of simultaneous transmission in partial bands in a CC, RFretuning requirement for partial band switching may be considered,wherein the partial band may indicate a bandwidth part.

In an example embodiment, Common PRB indexing may be employed at leastfor DL BWP configuration in RRC connected state. For example, areference point may be PRB 0, which may be common to one or morewireless devices sharing a wideband CC from network perspective,regardless of whether they are NB, CA, or WB wireless devices. In anexample, an offset from PRB 0 to the lowest PRB of the SS block accessedby a wireless device may be configured by high layer signaling, e.g.,via RMSI and/or wireless device-specific signaling. In an example, acommon PRB indexing may be for maximum number of PRBs for a givennumerology, wherein the common PRB indexing may be for RS generation forwireless device-specific PDSCH and/or may be for UL.

In an example embodiment, there may be an initial active DL/UL bandwidthpart pair to be valid for a wireless device until the wireless device isexplicitly (re)configured with bandwidth part(s) during or after RRCconnection is established. For example, the initial active DL/ULbandwidth part may be confined within the wireless device minimumbandwidth for the given frequency band. NR may supportactivation/deactivation of DL and UL bandwidth part by explicitindication at least in DCI. MAC CE based approach may be employed forthe activation/deactivation of DL and UL bandwidth part. In an example,NR may support an activation/deactivation of DL bandwidth part by meansof timer for a wireless device to switch its active DL bandwidth part toa default DL bandwidth part. For example, a default DL bandwidth partmay be the initial active DL bandwidth part defined above. The defaultDL bandwidth part may be reconfigured by the network.

In an example embodiment, when a wireless device performs measurement ortransmit SRS outside of its active BWP, it may be considered as ameasurement gap. For example, during the measurement gap, wirelessdevice may not monitor CORESET.

In an example embodiment, a SRS transmission in an active UL BWP mayemploy the same numerology as that configured for that BWP. For example,for LTE SRS sequences, NR may support wireless device specificconfigured bandwidth based on tree-like SRS bandwidth sets (e.g.,analogues to LTE). Parameters employed for configuring bandwidthallocation, e.g. whether or not CSRS and BSRS may be reused in awireless device specific manner. For example, for LTE SRS sequences, NRmay support to sound substantially all UL PRBs in a BWP.

In an example embodiment, a frequency-hopping for a PUCCH may occurwithin an active UL BWP for the wireless device, wherein there may bemultiple active BWPs, and the active BWP may refer to BWP associatedwith the numerology of PUCCH

In an example embodiment, for paired spectrum, base station mayconfigure DL and UL BWPs separately and independently for a wirelessdevice-specific serving cell for a wireless device. For example, foractive BWP switching using at least scheduling DCI, a DCI for DL may beemployed for DL active BWP switching and a DCI for UL may be employedfor UL active BWP switching. For example, NR may support a single DCIswitching DL and UL BWP jointly.

In an example, embodiment, for unpaired spectrum, base station mayjointly configure a DL BWP and an UL BWP as a pair, with the restrictionthat the DL and UL BWPs of a DL/UL BWP pair may share the same centerfrequency but may be of different bandwidths for a wirelessdevice-specific serving cell for a wireless device. For example, foractive BWP switching using at least scheduling DCI, a DCI for either DLor UL may be employed for active BWP switching from one DL/UL BWP pairto another pair. This may apply to at least the case where both DL & ULare activated to a wireless device in the corresponding unpairedspectrum. In an example, there may not be a restriction on DL BWP and ULBWP pairing.

In an example embodiment, for a wireless device, a configured DL (or UL)BWP may overlap in frequency domain with another configured DL (or UL)BWP in a serving cell.

In an example embodiment, for a serving cell, a maximal number of DL/ULBWP configurations may be for paired spectrum, for example, 4 DL BWPsand 4 UL BWPs. In an example, a maximal number of DL/UL BWPconfigurations may be for unpaired spectrum, for example, 4 DL/UL BWPpairs. In an example, a maximal number of DL/UL BWP configurations maybe for SUL, for example, 4 UL BWPs.

In an example embodiment, for paired spectrum, NR may support adedicated timer for timer-based active DL BWP switching to the defaultDL BWP. For example, a wireless device may start the timer when itswitches its active DL BWP to a DL BWP other than the default DL BWP. Inan example, a wireless device may restart the timer to the initial valuewhen it successfully decodes a DCI to schedule PDSCH(s) in its active DLBWP. For example, a wireless device may switch its active DL BWP to thedefault DL BWP when the timer expires.

In an example embodiment, for unpaired spectrum, NR may support adedicated timer for timer-based active DL/UL BWP pair switching to thedefault DL/UL BWP pair. For example, a wireless device may start thetimer when it switches its active DL/UL BWP pair to a DL/UL BWP pairother than the default DL/UL BWP pair. For example, a wireless devicemay restart the timer to the initial value when it successfully decodesa DCI to schedule PDSCH(s) in its active DL/UL BWP pair. In an example,a wireless device may switch its active DL/UL BWP pair to the defaultDL/UL BWP pair when the timer expires.

In an example embodiment, for an Scell, RRC signaling for Scellconfiguration/reconfiguration may indicate a first active DL BWP and/ora first active UL BWP when the Scell is activated. In an example, NR maysupport a Scell activation signaling that doesn't contain anyinformation related to the first active DL/UL BWP. In an example, for anScell, an active DL BWP and/or UL BWP may be deactivated when the Scellis deactivated. In an example, the Scell may be deactivated by an Scelldeactivation timer.

In an example embodiment, for an Scell, a wireless device may beconfigured with at least one of following: a timer for timer-basedactive DL BWP (or DL/UL BWP pair) switching, and/or a default DL BWP (orthe default DL/UL BWP pair) which may be employed when the timer isexpired, wherein the default DL BWP may be different from the firstactive DL BWP.

In an example, for Pcell, a default DL BWP (or DL/UL BWP pair) may beconfigured/reconfigured to a wireless device. In an example, if nodefault DL BWP is configured, the default DL BWP may be an initialactive DL BWP.

In an example embodiment, in a serving cell where PUCCH is configured, aconfigured UL BWP may comprise PUCCH resources.

In an example embodiment, for a wireless device in Pcell, a commonsearch space for at least RACH procedure may be configured in one ormore BWPs. For example, for a wireless device in a serving cell, acommon search space for group-common PDCCH (e.g. SFI, pre-emptionindication, etc.) may be configured in one or more BWPs

In an example embodiment, a DL (or UL) BWP may be configured to awireless device by resource allocation Type 1 with 1PRB granularity ofstarting frequency location and 1PRB granularity of bandwidth size,wherein the granularity may not imply that a wireless device may adaptits RF channel bandwidth accordingly.

In an example embodiment, for a wireless device, DCI format size itselfmay not be a part of RRC configuration irrespective of BWP activation &deactivation in a serving cell. For example, the DCI format size maydepend on different operations and/or configurations (if any) ofdifferent information fields in the DCI.

In an example embodiment, an initial active DL BWP may be defined asfrequency location and bandwidth of RMSI CORESET and numerology of RMSI,wherein PDSCH delivering RMSI may be confined within the initial activeDL BWP.

In an example embodiment, a wireless device may be configured with PRBbundling size(s) per BWP.

In an example embodiment, NR may support configuring CSI-RS resource onBWP with a transmission BW equal to or smaller than the BWP. Forexample, when the CSI-RS BW is smaller than the BWP, NR may support atleast the case that CSI-RS spans contiguous RBs in the granularity of NRBs. When CSI-RS BW is smaller than the corresponding BWP, it may be atleast larger than X RBs, wherein value of X is predefined. For example,the value of X may be the same or different for beam management and CSIacquisition. For example, the value of X may or may not benumerology-dependent.

For example, RSs for beam management of an active BWP may compriseCSI-RS, SS Blocks, and/or the like. A base station may transmit to awireless device one or more RRC messages comprising RS resourceconfiguration parameters indicating one or more CSI report setting forthe active BWP. The one or more CSI report setting may comprise one ormore RS resources and a report quantity indicator. The report quantityindicator may indicate that report of a reference signal received power(RSRP), precoding matrix indicator (PMI), channel quality indicator(CQI), rank indicator (RI), or CSI-RS resource index (CRI) is required.The RSRP may be a layer-1 RSRP report measured based on the one or moreCSI-RS resources. A RSRP report may be for beam management.CQI/PMI/RI/CRI report may be for CSI acquisition. The one or more RSRPreport may be measured based on the one or more CSI-RS resources of anactive BWP. The UE may transmit one or more CQI/PMI/RI/CRI report forthe active BWP. The one or more CQI/PMI/RI/CRI report may be based onthe one or more CSI-RS resources of the active BWP. The UE may transmitthe one or more RSRP report or the one or more CQI/PMI/RI/CRI reportbased on the report quantity indicator. In an example, when the reportquantity indicator indicates RSRP report is required, the UE maytransmit the one or more RSRP report. when the report quantity indicatorindicates CQI/PMI/RI/CRI report is required, the UE may transmit the oneor more CQI/PMI/RI/CRI report.

In an example embodiment, for FDD, base station may configure separatesets of bandwidth part (BWP) configurations for DL & UL per componentcarrier. In an example, a numerology of DL BWP configuration may beapplied to at least PDCCH, PDSCH & corresponding DMRS. A numerology ofUL BWP configuration may be applied to at least PUCCH, PUSCH &corresponding DMRS. In an example, for TDD, base station may configureseparate sets of BWP configurations for DL & UL per component carrier.In an example, a numerology of DL BWP configuration is applied to atleast PDCCH, PDSCH & corresponding DMRS. A numerology of UL BWPconfiguration is applied to at least PUCCH, PUSCH & corresponding DMRS.For example, when different active DL and UL BWPs are configured,wireless device may not retune the center frequency of channel BWbetween DL and UL.

In an example, a plurality of scheduling request (SR) configurations maybe configured for a bandwidth part (BWP) of a cell for a wirelessdevice. In an example, a wireless device may use SR resources configuredby a SR resource in the plurality of SR configurations in a BWP toindicate to the base station the numerology/TTI/service type of alogical channel (LCH) or logical channel group (LCG) that triggered theSR. In an example, the maximum number of SR configurations may be themaximum number of logical channels/logical channel groups.

In an example, there may be at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell. A BWP of a cell may beconfigured with a specific numerology/TTI. In an example, a logicalchannel and/or logical channel group that triggers SR transmission whilethe wireless device operates in one active BWP, the corresponding SR mayremain triggered in response to BWP switching.

In an example, the logical channel and/or logical channel group to SRconfiguration mapping may be (re)configured in response to switching ofthe active BWP. In an example, when the active BWP is switched, the RRCdedicated signaling may (re-)configure the logical channel and/orlogical channel group to SR configuration mapping on the new active BWP.

In an example, mapping between the logical channel and/or logicalchannel group to SR configuration may be configured when BWP isconfigured. RRC may pre-configure mapping between logical channel and/orlogical channel group to SR configurations for all the configured BWPs.In response to the switching of the active BWP, the wireless device mayemploy the RRC configured mapping relationship for the new BWP. In anexample, when BWP is configured, RRC may configure the mapping betweenlogical channel and SR configurations for the BWP.

In an example, sr-ProhibitTimer and SR_COUNTER corresponding to a SRconfiguration may continue and the value of the sr-ProhibitTimer and thevalue of the SR_COUNTER may be their values before the BWP switching.

In an example, a plurality of logical channel/logical channel group toSR-configuration mappings may be configured in a serving cell. A logicalchannel/logical channel group may be configured to be mapped to at mostone SR configuration per Bandwidth Part. In an example, a logicalchannel/logical channel group configured to be mapped onto multiple SRconfigurations in a serving cell may have one SR configuration active ata time, e.g., that of the active BWP. In an example, a plurality oflogical channel/logical channel group to SR-configuration mappings maybe supported in carrier aggregation (CA). A logical channel/logicalchannel group may be configured to be mapped to one (or more) SRconfiguration(s) in each of both PCell and PUCCH-SCell. In an example,in CA, a logical channel/logical channel group configured to be mappedto one (or more) SR configuration(s) in each of both PCell andPUCCH-SCell may have two active SR configurations (one on PCell and oneon PUCCH-SCell) at a time. In an example, The SR resource which comesfirst may be used.

In an example, a base station may configure one SR resource per BWP forthe same logical channel/logical channel group. If a SR for one logicalchannel/logical channel group is pending, it may be possible forwireless device to transmit SR with the SR configuration in another BWPafter BWP switching. In an example, the sr-ProhibitTimer and SR_COUNTERfor the SR corresponding to the logical channel/logical channel groupmay continue in response to BWP switching. In an example, when a SR forone logical channel/logical channel group is pending, the wirelessdevice may transmit the SR in another SR configuration corresponding tothe logical channel/logical channel group in another BWP after BWPswitching.

In an example, if multiple SRs for logical channels/logical channelgroups mapped to different SR configurations are triggered, the wirelessdevice may transmit one SR corresponding to the highest priority logicalchannel/logical channel group. In an example, the wireless device maytransmit multiple SRs with different SR configurations. In an example,SRs triggered at the same time (e.g., in the same NR-UNIT) by differentlogical channels/logical channel groups mapped to different SRconfigurations may be merged into a single SR corresponding to the SRtriggered by the highest priority logical channel/logical channel group.

In an example, when an SR of a first SR configuration is triggered by afirst logical channel/logical channel group while an SR proceduretriggered by a lower priority logical channel/logical channel group ison-going on another SR configuration, the later SR may be allowed totrigger another SR procedure on its own SR configuration, independentlyof the other on-going SR procedure. In an example, a wireless device maybe allowed to send triggered SRs for logical channels/logical channelgroups mapped to different SR configurations independently. In anexample, wireless device may be allowed to send triggered SRs for LCHscorresponding to different SR configurations independently.

In an example, dsr-TransMax may be independently configured per SRconfiguration. In an example, SR_COUNTER may be maintained for each SRconfiguration independently. In an example, a common SR_COUNTER may bemaintained for all the SR configurations per BWP.

In an example, PUCCH resources may be configured per BWP. The PUCCHresources in the currently active BWP may be used for UCI transmission.In an example, PUCCH resource may be configured per BWP. In an example,it may be necessary to use PUCCH resources in a BWP not currently activefor UCI transmission. In an example, PUCCH resources may be configuredin a default BWP and BWP switching may be necessary for PUCCHtransmission. In an example, a wireless device may be allowed to sendSR1 in BWP1, even though BWP1 is no longer active. In an example, thenetwork may reconfigure (e.g., pre-configure) the SR resources so thatboth SR1 and SR2 may be supported in the active BWP. In an example, ananchor BWP may be used for SR configuration. In an example, the wirelessdevice may send SR2 as “fallback”.

In an example, a logical channel/logical channel group mapped to a SRconfiguration in an active BWP may also be mapped to the SRconfiguration in another BWP to imply same or different information(e.g., numerology/TTI and priority).

In an example, a MAC entity may be configured with a plurality of SRconfigurations within the same BWP. In an example, the plurality of theSR configurations may be on the same BWP, on different BWPs, or ondifferent carriers. In an example, the numerology of the SR transmissionmay not be the same as the numerology that the logical channel/logicalchannel group that triggered the SR is mapped to.

In an example, for an LCH mapped to multiple SR configurations, thePUCCH resources for transmission of the SR may be on different BWPs ordifferent carriers. In an example, if multiple SRs are triggered, theselection of which configured SR configuration within the active BWP totransmit one SR may be up to wireless device implementation.

In an example, a single BWP may support multiple SR configurations. Inan example, multiple sr-ProhibitTimers (e.g., each for one SRconfiguration) may be running at the same time. In an example,drs-TransMax may be independently configured per SR configuration. In anexample, SR_COUNTER may be maintained for each SR configurationindependently.

In an example, a single logical channel/logical channel group may bemapped to zero or one SR configuration. In an example, PUCCH resourceconfiguration may be associated with an UL BWP. In an example, in CA,one logical channel may be mapped to none or one SR configuration perBWP.

In an example, the bandwidth part (BWP) may consist of a group ofcontiguous PRBs in the frequency domain. The parameters for each BWPconfiguration may include numerology, frequency location, bandwidth size(e.g., in terms of PRBs), CORESET (e.g., required for each BWPconfiguration in case of single active DL bandwidth part for a giventime instant). In an example, one or multiple BWPs may be configured foreach component carrier when the wireless device is in RRC connectedmode.

In an example, when a new BWP is activated, the configured downlinkassignment may be initialized (if not active) or re-initialized (ifalready active) using PDCCH.

In an example, for uplink SPS, the wireless device may initialize orre-initialize the configured uplink grant when switching from one BWP toanther BWP. When a new BWP is activated, the configured uplink grant maybe initialized (if not active) or re-initialized (if already active)using PDCCH.

In an example, for type 1 uplink data transmission without grant, theremay be no L1 signaling to initialize or re-initialize the configuredgrant. The wireless device may not assume the type 1 configured uplinkgrant is active when the BWP is switched even if it's already active inthe previous BWP. The type 1 configured uplink grant may bere-configured using RRC dedicated signaling when the BWP is switched. Inan example, when a new BWP is activated, the type 1 configured uplinkgrant may be re-configured using dedicated RRC signaling.

In an example, if SPS is configured on the resources of a BWP and thatBWP is subsequently deactivated, the SPS grants or assignments may notcontinue. In an example, when a BWP is deactivated, all configureddownlink assignments and configured uplink grants using resources ofthis BWP may be cleared. In an example, the MAC entity may clear theconfigured downlink assignment or/and uplink grants upon receivingactivation/deactivation of BWP.

In an example, the unit of drx-RetransmissionTimer anddrx-ULRetransmissionTimer may be OFDM symbol corresponding to thenumerology of the active BWP. In an example, if a wireless device ismonitoring an active DL BWP for a long time without activity, thewireless device may move to default BWP for power saving. In an example,a BWP inactivity timer may be introduced to switch active BWP to defaultBWP after a certain inactive time.

In an example, autonomous switching to DL default BWP may consider bothDL BWP inactivity timer and/or DRX timers (e.g., HARQ RTT and DRXretransmission timers). In an example, DL BWP inactivity timer may beconfigured per MAC entity. In an example, a wireless device may beconfigured to monitor PDCCH in a default BWP at least when wirelessdevice uses long DRX cycle.

In an example, PHR may not be triggered due to the switching of BWP. Inan example, the support of multiple numerologies/BWPs may not impact PHRtriggers. In an example, PHR may be triggered upon BWP activation. In anexample, a prohibit timer may start upon PHR triggering due to BWPswitching. PHR may not be triggered due to BWP switching while theprohibit timer is running. In an example, PHR may be reported peractivated/deactivated BWP.

In an example, PDCP duplication may be in an activated state while thewireless device receives the BWP deactivation command. In an example,when the BWP which the PDCP duplication is operated on is deactivated,the PDCP duplication may not be deactivated, but the PDCP entity maystop sending the data to the deactivated RLC buffer.

In an example, RRC signalling may configure one BWP to be activated whenthe SCell is activated. Activation/deactivation MAC CE may be used toactivate both the SCell and the configured BWP. In an example, one HARQentity may serve different BWP within one carrier.

In an example, for a wireless device-specific serving cell, one or moreDL BWPs and one or more UL BWPs may be configured by dedicated RRC for awireless device. In an example, a single scheduling DCI may switch thewireless device's active BWP from one to another. In an example, anactive DL BWP may be deactivated by means of timer for a wireless deviceto switch its active DL bandwidth part to a default DL bandwidth part.

In an example, narrower BWP may be used for DL control monitoring andwider BWP may be used for scheduled data. In an example, small data maybe allowed in narrower BWP without triggering BWP switching.

In an example embodiment, for a wireless device with a RRC connectedmode, RRC signalling may support to configure one or more BWPs (both forDL BWP and UL BWP) for a serving cell (PCell, PSCell). For example, RRCsignalling may support to configure 0, 1 or more BWPs (both for DL BWPand UL BWP) for a serving cell SCell (at least 1 DL BWP). In an example,for a wireless device, the PCell, PSCell and each SCell may have asingle associated SSB in frequency. A cell defining SS block may bechanged by synchronous reconfiguration for PCell/PSCell and SCellrelease/add for the SCell. For example, a SS block frequency which needsto be measured by the wireless device may be configured as individualmeasurement object (e.g., one measurement object corresponds to a singleSS block frequency). the cell defining SS block may be considered as thetime reference of the serving cell, and for RRM serving cellmeasurements based on SSB, for example, irrespective of which BWP isactivated.

In an example, embodiment, one or more RRC timers and counters relatedto RLM may not be reset when the active BWP is changed.

In an example embodiment, an SR configuration may comprise a collectionof sets of PUCCH resources across different BWPs and cells, wherein percell, at any given time there may be at most one usable PUCCH resourceper LCH, and/or this may be applicable to the case of one singleLTE-like set of SR PUCCH resources being configured per LCH per BWP, andone BWP being active at a time.

In an example embodiment, BWP switching and cell activation/deactivationmay not interfere with the operation of the counter and timer. Forexample, when a BWP is deactivated, the wireless device may or may notstop using configured downlink assignments and/or configured uplinkgrants using resources of the BWP. In an example, the wireless devicemay suspend the configured grants of the or clear it. In an example, thewireless device may not suspend the configured grants of the or may notclears it.

In an example embodiment, a new timer (BWP inactivity timer) may beemployed to switch active BWP to default BWP after a certain period ofinactive time. The BWP inactivity timer may be independent from the DRXtimers.

In an example embodiment, on the BWP that is deactivated, wirelessdevice may not transmit on UL-SCH on the BWP. In an example, on the BWPthat is deactivated, wireless device may not

In an example, on the BWP that is deactivated, wireless device may notmonitor the PDCCH on the BWP. In an example, on the BWP that isdeactivated, wireless device may not transmit PUCCH on the BWP. In anexample, on the BWP that is deactivated, wireless device may nottransmit on PRACH on the BWP. In an example, on the BWP that isdeactivated, wireless device may not flush HARQ buffers when doing BWPswitching.

In an example embodiment, a wireless device may receive one or more RRCmessages/signaling from a base station. The one or more RRCmessages/signaling may cause configuration of at least one UL BWP, atleast one DL BWP, and one or more configured grants for a cell. DCIgrants may be of at least two types: configured grants and dynamicgrants. The one or more configured grants may be semi-persistentscheduling (SPS), Type 1 grant-free (GF) transmission/scheduling, and/orType 2 GF transmission/scheduling. A configured grant provides periodresource allocation/assignment for one or more wireless devices. Awireless device does not need to receive DCI for transmission/receptionvia each resource allocation/assignment. In an example, one or moreconfigured grants may be configured per UL BWP. For example, one or moreradio resources associated with one or more configured grants may not bedefined/assigned/allocated across two or more UL BWPs. Configured grantsare activated/initialized and deactivated/released/cleared by the basestation and wireless device. Dynamic DCI grants may provide uplinkresources for one or more TTIs.

In an example embodiment, a wireless device may be configured a BWPinactivity timer for a downlink bandwidth part of a cell. For example,the BWP inactivity timer may be associated with an active DL BWP of thecell. For example, when an active DL BWP is not a default DL BWP in thecell, the BWP inactivity timer may be running. In an example embodiment,a BWP inactivity timer (e.g., DL BWP inactivity timers) may (re)startwhen an active BWP (e.g., an active DL BWP) is switched to a non-defaultBWP (e.g., a non-default DL BWP). In an example, the BWP inactivitytimer (e.g., DL BWP inactivity timers) may stop (or be disabled) when anactive BWP (e.g., an active DL BWP) is switched to a default BWP (e.g.,a default DL BWP). In an example, when the BWP inactivity timer expires,an active BWP (e.g., an active DL BWP) may switched to a default BWP(e.g., a default DL BWP).

In an example embodiment, a wireless device may be configured with oneor more configured grants on an UL BWP for a cell. For example, awireless device may be configured with a BWP inactivity timer (e.g., DLBWP inactivity timers) for the cell. The BWP inactivity timer (e.g., DLBWP inactivity timers) may start when an active DL BWP is not a defaultBWP. The BWP inactivity timer (e.g., DL BWP inactivity timers) may startwhen an active DL BWP is not a default BWP and an UL BWP, that is a pairof an active DL BWP, becomes active.

In an example embodiment, an BWP may be active during a period of timewhen a BWP inactivity timer is running. For example, a base station maytransmit a control message to a wireless device to configure a firsttimer value (or a first counter value) of an BWP inactivity timer. Thefirst timer value may determine how long a BWP inactivity timer runs,e.g., a period of time that a BWP inactivity timer runs. For example,the BWP inactivity timer may be implemented as a count-down timer from afirst timer value down to a value (e.g., zero). In an exampleembodiment, the BWP inactivity timer may be implemented as a count-uptimer from a value (e.g., zero) up to a first timer value. In an exampleembodiment, the BWP inactivity timer may be implemented as adown-counter from a first counter value down to a value (e.g., zero). Inan example embodiment, the BWP inactivity timer may be implemented as acount-up counter from a value (e.g., zero) up to a first counter value.For example, a wireless device may restart a BWP inactivity timer whenthe wireless device receives (and/or decodes) a DCI to schedule PDSCH(s)in its active BWP (e.g., its active DL BWP, and/or UL/DL BWP pair).

FIG. 25 shows example of BWP switching based on BWP inactivity timer. AUE may receive RRC message comprising parameters of at least one SCelland one or more BWP configuration associated with the at least oneSCell. Among the one or more BWPs, at least one BWP may be configured asthe first active BWP (e.g., BWP 1 in the figure), one BWP as the defaultBWP (e.g., BWP 0 in the figure). The UE may receive a MAC CE to activatethe Scell at the n^(th) subframe. The UE may start thesCellDeactivationTimer, and start reporting CSI for the SCell, and/orstart reporting CSI for the first active BWP of the SCell at a firstavailable CSI resource on or after the (n+8)^(th) subframe. The UE maystart the BWP inactivity timer when receiving a DCI indicating switchingBWP from BWP 1 to BWP 2, at the (n+8+k)^(th) subframe. When receiving aPDCCH indicating DL scheduling on BWP 2, for example, at the(n+8+k+m)^(th) subframe, the UE may restart the BWP inactivity timer.The UE may switch back to the default BWP (0) when the BWP inactivitytimer expires, at the (n+8+k+m+1)^(th) subframe. The UE may deactivatethe SCell when the sCellDeactivationTimer expires. Employing the BWPinactivity timer may further reduce UE's power consumption when the UEis configured with multiple cells with each cell having wide bandwidth(e.g., 1 GHz). The UE may only transmit on or receive from a bandwidthBWP (e.g., 5 MHz) on the PCell or SCell when there is no activity on anactive BWP.

In an example, a UE may receive one or more RRC messages configuring afirst active BWP and a default BWP for a SCell. The first active BWP andthe default BWP may be different, for example, as shown in FIG. 25, thefirst active BWP is BWP 0, and the default BWP is BWP 1. When receivinga MAC CE activating the SCell, the UE may activate the first active BWP(BWP 1), e.g., by monitoring one or more PDCCH and/or transmittinguplink signals on the first active DL or UL BWP. In an example, the UEmay stay on the first active BWP (BWP 1) until receiving a DCIindicating active BWP change, and starting the BWP inactivity timer. Inthis case, it may not be power efficient, since the UE may keepmonitoring the PDCCH on the first active BWP, even though there may beno activity on the first active BWP until receiving a DCI indicating aBWP change. There is a need to have mechanisms to reduce powerconsumption for a UE when an SCell activated with multiple BWPs.

FIG. 26 shows an example embodiment. A UE may receive one or more RRCmessages comprising at least configuration parameters of a plurality ofcells. The plurality of cells may comprise a PCell and at least oneSCell. The configuration parameters of the at least one SCell maycomprise at least one of: one or more BWPs associated with one or moreradio resource configuration (e.g., frequency location, bandwidth,subcarrier spacing, cyclic prefix, one or more CSI-RS resourceconfiguration); at least a first BWP identifier indicating a firstactive BWP; a second BWP identifier indicating a default BWP; a BWPinactivity timer with a timer value; and/or an SCell deactivation timerwith a timer value. The BWP inactivity timer value may be configured percell or per base station in an RRC message, or may be a pre-definedvalue. The SCell deactivation timer may be configured for each SCellwith a different/same value. In an example, the SCell deactivation timermay be configured for all SCells with a same value in an RRC message, oras a pre-defined value.

The UE may receive an SCell activation/deactivation MAC CE comprisingparameters indicating activation or deactivation of the at least oneSCell at the n^(th) subframe. In an example, a UE may receive an SCellactivation/deactivation DCI indicating activation or deactivation of theat least one SCell at the n^(th) subframe. The UE may start or restartthe SCell deactivation timer at the (n+k)^(th) subframe, in response toreceiving the SCell activation/deactivation MAC CE or DCI. In anexample, the UE may start the BWP inactivity timer at the (n+k+m)^(th)subframe, in response to receiving the SCell activation/deactivation MACCE or DCI, if the first active BWP is different from the default BWP. Inan example, the UE may start transmitting CSI report for the firstactive BWP at a first available CSI resources on or after the (n+k)^(th)subframe. In an example, the UE may start transmitting CSI report forthe first active BWP at a first available CSI resources on or after the(n+k+m)^(th) subframe. The first time offset (e.g., k value) betweenreceiving the SCell activation/deactivation MAC CE or DCI and startingthe SCell deactivation timer may be configured in a RRC message, orpreconfigured as a fixed value.

The second time offset (e.g., m value) between starting the SCelldeactivation timer and starting the BWP inactivity timer may beconfigured in an RRC message, or predefined as a fixed value. Forexample, the first time offset may be configured as zero if a DCI isused to activate an SCell in case that a UE is capable of activating theSCell with a first time offset of zero. The second time offset may bepredefined or configured as zero if the time for SCell activation issame as the time for BWP activation, then the UE may start the SCelldeactivation timer and BWP inactivity timer (if the first active BWP isdifferent from the default BWP) at the same time. In the embodiment,when activating an SCell with multiple BWPs, the UE may switch to thedefault BWP when the BWP inactivity timer expires, even withoutreceiving a DCI indicating BWP change, therefore reducing the powerconsumption. The configurable or predefined time offset for SCellactivation and BWP activation may give the gNB more flexibility oncontrolling SCell activation and BWP activation, and allow different UEswith different capability (e.g., on BWP switch) to change BWP correctly.

In an example, when receiving a second DCI indicating an active BWPchange, a UE may start or restart the BWP inactivity timer depending onwhether the new active BWP is the default BWP. For example, in FIG. 26,a UE may receive a second DCI indicating active BWP change from BWP 1 toBWP 2, at the (n+k+m+1)^(th) subframe. The UE may start or restart theBWP inactivity timer if the new active BWP is not the default BWP. In anexample, the UE may start or restart the BWP inactivity timer at thesame subframe, e.g., the (n+k+m+1)^(th) subframe. In an example, whenthe UE may have a slow BWP switch, the UE may start or restart the BWPinactivity timer at the (n+k+m+1+0)^(th) subframe. The time offset(e.g., 0 value) between receiving the second DCI and starting BWPinactivity timer may be configured or predefined. The time offset may bea transition gap. The transition gap may be a time period between afirst time when receiving the second DCI and a second time when thewireless device completes BWP switching from BWP 1 to BWP 2. Theconfigurable time offset between receiving BWP change DCI and startingthe BWP inactivity timer may provide the gNB more flexibility oncontrolling BWP change, and allow different UEs with differentcapability (e.g., on BWP switch) to change BWP correctly.

In an example, a UE may receive the second DCI indicating active BWPchange from an active BWP to a default BWP, for example, in FIG. 26, aUE may receive the second DCI indicating active BWP change from BWP 1 toBWP 0. The UE may stop the BWP inactivity timer, in response toreceiving the second DCI. With the embodiment, stopping the BWPinactivity timer when switching an active BWP to the default BWP mayreduce unnecessary BWP inactivity timer management at the gNB and theUE.

In an example, a UE may restart the BWP inactivity timer when the UEreceives a DCI indicating PDSCH scheduling for an active DL BWP. Whenthe UE does not receive DCI(s) for PDSCH scheduling for a period oftime, the BWP inactivity timer may expire and the UE may switch to thedefault BWP as the active BWP. For some services, the UE may need tostay on an active BWP even if there is no DCI for PDSCH schedulingduring a period of time. For example, the UE may receive a resourceassignment (e.g. via RRC, MAC and/or DCI) for configured PDSCHtransmission (e.g., SPS transmission, or grant-free transmission) fromthe base station for periodic transmissions via PDSCH. Since there is noDCI for PDSCH scheduling during a period of time, the BWP inactivitytimer may expire. The UE may switch to the default BWP as an active BWP.In this example, the configured PDSCH transmission may be interrupteddue to switching the active BWP. There is a need to implement amechanism for maintaining uninterrupted PDSCH transmission even if a DCIis not received during a period of time.

In existing technologies, a base station may maintain uninterruptedPDSCH transmission on the active BWP by frequently transmitting DCIs forPDSCH or PUSCH scheduling to restart the BWP inactivity timer so thatthe BWP inactivity timer does not expire. Frequently transmitting theDCIs may increase downlink control channel overhead. Implementation ofthe existing technologies may increase battery power consumption and UEprocessing requirements for monitoring downlink control channel for theDCIs. There is need for enhanced mechanisms to reduce downlink controlchannel overhead, UE battery power consumption and processingrequirements when uninterrupted data transmission on a BWP is required.

Example embodiments may enable a wireless device and/or a base stationto maintain an active state of an active BWP for the wireless devicewithout sending DCI(s) for PDSCH scheduling. Example embodimentsimplement signaling and BWP inactivity timer management mechanisms thatmay reduce downlink control overhead. Example embodiment further reducesRRC signaling overhead by implementing an enhanced mechanism for RRCconfiguration signaling for BWP configuration. Example embodiment mayreduce power consumption and processing for blind decoding of DCI by theUE.

In an example, a UE may receive from a base station, one or more RRCmessages comprising configuration parameters of a cell of a plurality ofcells. For example, the cell may be a primary cell or a secondary cell.The configuration parameters may comprise at least one of: one or moreBWPs associated with one or more radio resource configuration (e.g.,frequency location, bandwidth, subcarrier spacing, cyclic prefix, one ormore CSI-RS resource configuration); a first BWP identifier indicating afirst active BWP; a second BWP identifier indicating a default BWP; afirst timer value for a BWP inactivity timer; a second timer value for acell deactivation timer (e.g. BWP is a for an SCell). The first timervalue for the BWP inactivity timer may be set to a first value (e.g.,“infinite”). In response to the first timer value set to the first valuein the one or more RRC messages, the UE may disable the BWP inactivitytimer. The UE may maintain a state of an active BWP in response todisabling the BWP inactivity timer. In an example, the UE may activate acell of the plurality of cells when receiving a MAC CE or DCI indicatingan activation of the cell, when the cell is a secondary cell. The UE maymonitor a downlink control channel of an active BWP (e.g. a first activeBWP configured in one or more RRC messages) of the cell. The UE mayreceive a downlink control information on the downlink control channelduring the monitoring. The UE may receive data packets based on thedownlink control information indicating downlink assignments. The UE maytransmit data packets based on the downlink control informationindicating uplink grants. The UE may keep monitoring the downlinkcontrol channel of the active BWP continuously based on DRX operationbeing not configured. The UE may monitor, during DRX active time, thedownlink control channel of the active BWP discontinuously in responseto DRX operation being configured. The UE may maintain the state of theactive BWP until receiving a second downlink control informationindicating switching the active BWP. Example embodiment may maintain astate of an active BWP without a need for transmitting by a base stationa DCI triggering restarting the BWP inactivity timer, and may reduce DCIsignal overhead. The example embodiment may require an RRC informationelement for configuring BWP inactivity timer. This may requireadditional overhead for transmission of RRC message to the wirelessdevice.

In an example, a UE may receive from a base station, one or more firstRRC messages comprising configuration parameters of a cell. Theconfiguration parameters may comprise at least one of: one or more BWPsassociated with one or more radio resource configuration (e.g.,frequency location, bandwidth, subcarrier spacing, cyclic prefix, one ormore CSI-RS resource configuration); a first BWP identifier indicating afirst active BWP; a second BWP identifier indicating a default BWP; afirst timer value for a BWP inactivity timer. The first timer value forthe BWP inactivity timer may be set to a first value (e.g., “infinite”).In response to the first timer value set to the first value in the oneor more RRC messages, the UE may disable the BWP inactivity timer. TheUE may maintain a state of an active BWP in response to disabling theBWP inactivity timer. Example embodiment may maintain a state of anactive BWP without a need for transmitting by a base station a DCItriggering restarting the BWP inactivity timer, and may reduce DCIsignal overhead. The example embodiment may require an RRC informationelement for configuring BWP inactivity timer. This may requireadditional overhead for transmission of RRC message to the wirelessdevice.

In an enhanced example embodiment both DCI and RRC signaling overheadmay be further reduced. In an example, the BWP inactivity timer may beabsent in the one or more RRC messages when a UE is configured withmultiple BWPs. The UE may disable the BWP inactivity timer in responseto receiving the one or more RRC messages comprising configurationparameters of multiple BWPs, where the BWP inactivity timer is absent inthe configuration parameters. The UE may maintain an active state of anactive BWP in response to disabling the BWP inactivity timer. The UE maymaintain the active state of the active BWP until receiving a commandindicating a BWP switching.

Example embodiments may enable a wireless device and/or a base stationto maintain an active state of an active BWP for the wireless devicewithout sending RRC BWP inactivity timer parameter and additional DCI(s)for PDSCH scheduling. Example embodiments implement signaling and BWPinactivity timer management mechanisms that may reduce downlink controloverhead. Example embodiment further reduces RRC signaling overhead byimplementing an enhanced mechanism for RRC configuration signaling forBWP configuration. Example embodiment may reduce power consumption andprocessing for blind decoding of DCI by the UE.

In an example, the UE may receive a first RRC message comprising firstconfiguration parameters of a plurality of BWPs of a cell. The pluralityof BWPs may comprise a first BWP and a default BWP. The firstconfiguration parameters may comprise a timer value for a BWP inactivitytimer. The UE may activate the first BWP in response to receiving afirst downlink control information indicating a downlink assignment oran uplink grant on the first BWP. The UE may start the BWP inactivitytimer based on the timer value. The UE may start the BWP inactivitytimer with the timer value. the UE may monitor, while the BWP inactivitytimer is running, a downlink control channel on the first BWP. In anexample, the UE may receive a second RRC message comprising secondconfiguration parameters of the plurality of BWPs of the cell.

The second configuration parameters may not comprise the BWP inactivitytimer. The BWP inactivity timer may be absent in the secondconfiguration parameters. In response to the second RRC message, the UEmay disable the BWP inactivity timer. The UE may stop (or disable) theBWP inactivity timer in response to the second RRC message. The UE maymaintain the active state of the first BWP in response to disabling (orstopping) the BWP inactivity timer. The UE may maintain the active stateof the first BWP without switching to the default BWP in response to thesecond RRC message. The UE may maintain the active state of the firstBWP until receiving a command indicating a BWP switching. The commandmay be an RRC message, a MAC CE, or a downlink control information. Inan example, the UE may switch to a second BWP as an active BWP from thefirst BWP in response to receiving a second downlink control informationindicating switching from the first BWP to the second BWP. The UE maymaintain the active state of the first BWP until receiving a commandindicating a deactivation of the cell, if the cell is a secondary cell.The UE may maintain the active state of the first BWP until receiving athird RRC message indicating change of one or more configurationparameters of the multiple BWPs of the cell. Example embodiments mayprovide methods to maintain a state of an active BWP by disabling theBWP inactivity timer. Maintaining the state of the active BWP may bebeneficial for uninterrupted downlink data transmission.

Example embodiments may enable a wireless device and/or a base stationto maintain an active state of an active BWP for the wireless devicewithout sending RRC BWP inactivity timer parameter and additional DCI(s)for PDSCH scheduling. Example embodiments implement signaling and BWPinactivity timer management mechanisms that may reduce downlink controloverhead. Example embodiment further reduces RRC signaling overhead byimplementing an enhanced mechanism for RRC configuration signaling forBWP configuration. Example embodiment may reduce power consumption andprocessing for blind decoding of DCI by the UE.

FIG. 27 shows an example embodiment. In an example, a UE (e.g., UE inFIG. 27) may receive from a base station (e.g., Base Station in FIG.27), a first RRC message comprising first configuration parameters of aplurality of BWPs. The first configuration parameters may comprise atimer value for a BWP inactivity timer. The plurality of BWPs maycomprise a first BWP and a default BWP. The UE may receive a firstdownlink control information via a downlink control channel (e.g.,physical downlink control channel) indicating an activation of the firstBWP. In response to the first downlink control information, the UE mayactivate the first BWP, start the BWP inactivity timer with the timervalue, and/or monitor the downlink control channel on the first BWP. TheUE may receive a second RRC message comprising second configurationparameters of the plurality of BWPs. The UE may determine that the BWPinactivity timer is absent in the second configuration parameters. Inresponse to the BWP inactivity timer being absent in the secondconfiguration parameters, the UE may disable (or stop) the BWPinactivity timer. The UE may maintain the active state of the first BWP(e.g., without switching to the default BWP). The UE may transmit orreceive data packets on the first BWP when the UE maintains the activestate of the first BWP.

In an example, transmission of the first RRC message may optional in theembodiment. The first RRC message may or may not be transmitted. In thiscase, when receiving the second RRC message, the wireless device maydetermine that the BWP inactivity timer is absent in the secondconfiguration parameters of the second RRC message. In response to thedetermining, the UE may disable (or stop) the BWP inactivity timer. TheUE may maintain the active state of the first BWP (e.g., withoutswitching to the default BWP). The UE may transmit or receive datapackets on the first BWP when the UE maintains the active state of thefirst BWP.

FIG. 28A shows an example flowchart of BWP management of a base station.At 2810, a base station may transmit to a wireless device, a first RRCmessage comprising first configuration parameters of BWPs. The firstconfiguration parameters may comprise a parameter of a BWP inactivitytimer. The parameter may be a timer value for the BWP inactivity timer.At 2820, the base station may transmit to the wireless device a firstcommand indicating an activation of a first BWP of the BWPs. Thewireless device may activate the first BWP and start the BWP inactivitytimer in response to the first command. At 2830, the base station maydetermine a disabling of the BWP inactivity timer and/or a maintainingan active state of the first BWP for the wireless device. In an example,the base station may determine the disabling of the BWP inactivity timerand/or the maintaining the active state of the first BWP when the basestation determines an activation of a semi-persistent scheduling or aconfiguration grant, or the base station determines to communicate withthe wireless device on the first BWP for some type of services (e.g.,URLLC, V2X, and/or IoT).

At 2840, the base station may transmit, in response to the determining,a second RRC message comprising second configuration parameters of theBWPs, the parameter of the BWP inactivity timer being absent in thesecond configuration parameters. In response to receiving the second RRCmessage, the wireless device may disable (or stop) the BWP inactivitytimer and maintain the active state of the first BWP. The wirelessdevice may maintain the active state of the first BWP until receiving asecond command indicating a BWP switching. In an example, some blocks(2810-2040) in FIG. 28A may be optional in one of the embodiments. In anexample, 2810 and/or 2820 in FIG. 28A may be optional for reducingsignaling overhead for the transmission of the first RRC messages. Inthis case, the base station may determine a disabling of the BWPinactivity timer and/or a maintaining an active state of the first BWPfor the wireless device. The base station may determine the disabling ofthe BWP inactivity timer and/or the maintaining the active state of thefirst BWP when the base station determines an activation of asemi-persistent scheduling or a configuration grant, or the base stationdetermines to launch on the first BWP some type of services (e.g.,URLLC, V2X, and/or IoT). At 2840, the base station may transmit, inresponse to the determining, a second RRC message comprising secondconfiguration parameters of the BWPs, the parameter of the BWPinactivity timer being absent in the second configuration parameters. Inresponse to receiving the second RRC message, the wireless device maydisable (or stop) the BWP inactivity timer and maintain the active stateof the first BWP. The wireless device may maintain the active state ofthe first BWP until receiving a second command indicating a BWPswitching.

FIG. 28B shows an example flowchart of BWP inactivity timer managementat a wireless device. At 2850, a wireless device may receive from a basestation, one or more RRC messages comprising configuration parameters ofone or more BWPs. At 2860, the wireless device may determine whether aBWP inactivity timer information element (IE) is absent in the one ormore RRC messages. In an example, if the BWP inactivity timer IE ispresent in the one or more RRC messages, at 2870, the wireless devicemay enable the BWP inactivity timer. The wireless device may start orrestart the BWP inactivity timer in response to receiving a DCIindicating a downlink assignment or an uplink grant on an active BWP. Inan example, if the BWP inactivity timer IE is absent in the one or moreRRC messages, at 2880, the wireless device may disable a BWP inactivitytimer. The wireless device may maintain an active state of an activeBWP, in response to disabling the BWP inactivity timer.

In an example, a UE may receive a downlink control information via adownlink control channel. The downlink control information may comprisea plurality of fields, with downlink radio resource allocation fieldsbeing absent, or uplink radio resource allocation fields being absent.The DCI may not comprise any downlink resource grant or uplink resourcegrant. The downlink or uplink radio resource allocation fields maycomprise a frequency resource allocation field and/or a time resourceallocation field. The downlink control information may indicate at leastone of: power control command; CSI report; downlink control resource setchange; uplink control resource set change; SRS transmission; beammanagement; and/or SCell activation/deactivation. The downlink controlinformation may indicate an active BWP, without downlink or uplinkresource allocation indication.

In existing technologies, BWP inactivity timer may be started orrestarted when the DCI comprises downlink assignment or uplink grant andBWP inactivity timer is not started when the DCI does not comprisedownlink assignment or uplink grant. Example embodiment enhancesexisting BWP timer management mechanisms to reduce unnecessary bandwidthpart switching. In an example embodiment, the behavior of UE may bedefined for both wireless device and base station. The gNB and the UEmay remain in-sync with regards to the BWP inactivity timer and/orwhether the UE switching the active BWP to the default BWP. Exampleembodiments may enable the UE to remain on the active BWP duringextended time period when receiving the downlink control informationwhich does not comprise downlink or uplink resource allocationindication.

In an example, a UE may receive one or more RRC message comprisingconfiguration parameters of a cell of a plurality of cells. Theplurality of cells comprising a primary cell and a secondary cell. Theconfiguration parameters of the cell may comprise at least one of: BWPsassociated with radio resource configuration (e.g., frequency location,bandwidth, subcarrier spacing, cyclic prefix, CSI-RS resourceconfiguration); a first BWP identifier indicating a first active BWP; asecond BWP identifier indicating a default BWP; a BWP inactivity timerwith a first timer value; a SCell deactivation timer with a second timervalue (e.g. when the cell is the secondary cell). In an example, the UEmay receive a SCell activation/deactivation MAC CE comprising parametersindicating activation or deactivation of the secondary cell. In anexample, a UE may receive a SCell activation/deactivation DCI indicatingactivation or deactivation of the secondary cell. In an example, the UEmay start the BWP inactivity timer, in response to receiving the SCellactivation/deactivation MAC CE or DCI. In an example, the UE may notmaintain a deactivation timer for a PCell.

In an example, when a UE receives a DCI for switching an active BWP, theUE may restart the BWP inactivity timer. When a UE receives a DCIcomprising a DL scheduling on PDSCH of the active BWP, the UE maystart/restart the BWP inactivity timer.

In an example, when a UE receives one or more signals comprising anindication of an active BWP, the UE may restart the BWP inactivitytimer. The active BWP indicated in the active BWP indication may be sameor different as a previous active BWP before receiving the one or moresignals. In an example, the one or more signals may comprise a downlinkcontrol information. The downlink control information may comprise aplurality of fields, with downlink radio resource allocation fieldsbeing absent, or uplink radio resource allocation fields being absent.The downlink control information may not comprise a downlink radioresource allocation field and/or an uplink radio resource allocationfield. The downlink control information may indicate at least one of:power control command; CSI report; downlink control resource set change;uplink control resource set change; SRS transmission; beam management;and/or SCell activation/deactivation. The downlink control informationmay indicate an active BWP, without downlink or uplink resourceallocation indication. In an example, the UE may restart the BWPinactivity timer in response to receiving the one or more signals, if afirst active BWP indicated in the one or more signals is same as acurrent BWP. The current BWP may be a BWP for DL transmission or ULtransmission before receiving the one or more signals. In an example,the UE may stop the BWP inactivity timer, if the active BWP indicated inthe one or more signals is same as the default BWP.

In an example, when configured with multiple beams (e.g., beamsassociated with SSBs in FIG. 15 and/or beams associated with CSI-RS inFIG. 17) on a cell, a UE may transmit to a base station one or more beamreport of the cell. The one or more beam report may comprise one or moreRSRP report of one or more beams (identified by an SSB or a CSI-RS) ofthe cell. In an example, a cell may be configured with multiple BWPs.Base station transmit data to a wireless device via one or more beamsconfigured on a bandwidth part.

In existing technologies, bandwidth part and beam management processesmay not be fully integrated. For example, if a wireless device switchesfrom a first BWP to a second BWP as an active BWP, beam report for thefirst BWP may be out-of-date and not accurate for the second BWP. Inorder to update beam pair link between the base station and the UE, thebase station may need to transmit to the UE one or more control signalsinstructing the UE to transmit one or more beam report for the secondBWP, after the UE completes switching to the second BWP. The basestation may need to transmit additional signaling to configure and/oractivate beam report on the second bandwidth part. In the existing beammanagement procedure, when switching the active BWP, the beam pair linksetup procedure may take extra time to finish, which may result indownlink data scheduling delay. This may increase signaling overhead andmay delay transmission of beam reports for the second bandwidth part.There is a need to implement enhanced beam report mechanisms whenmultiple BWPs are configured for a cell.

Example embodiments may provide enhanced mechanisms to reduce the beampair link setup procedure when switching from a first bandwidth part toa second bandwidth part as an active BWP. In an example embodiment, awireless device may transmit one or more beam reports for a new activeBWP (e.g. the second BWP) in response to switching to the second BWP asthe active BWP, without a need for waiting to receive the one or moresignaling (e.g., indicating the UE to transmit the beam report). Exampleembodiment may provide methods and systems enabling enhanced BWPscheduling for the base station and wireless device. Example embodimentmay reduce downlink and uplink scheduling delay when an active BWPchanges.

In an example, a UE may receive one or more RRC messages comprisingconfiguration parameters of a plurality of BWPs of a cell. Theconfiguration parameters may comprise at least one of: frequencylocation, bandwidth, subcarrier spacing, cyclic prefix, reference signal(RS) resource configuration parameters; a first BWP identifierindicating a first BWP; a second BWP identifier indicating a defaultBWP; a BWP inactivity timer with a timer value. The wireless device mayreceive a first DCI indicating activation of the first BWP. The UE mayactivate the first BWP in response to the first DCI. The UE may switchfrom the first BWP to a second BWP in response to switching to thesecond BWP as an active BWP. For example, the UE may receive a secondDCI indicating the switching. In response to activating the second BWP,the UE may transmit one or more RSRP report for the second BWP (e.g.without the need for base station to transmit any additional signaling).The one or more RSRP report may be measured based on the one or more RSresources of the second BWP. This may reduce downlink and uplinkscheduling delay and may reduce control signaling when an active BWPchanges.

In an example, when receiving a second DCI indicating an active BWPchange to the second BWP. The UE may start or restart the BWP inactivitytimer depending on whether the second BWP is the default BWP. The UE maystart or restart the BWP inactivity timer if the second BWP is not thedefault BWP. The UE may receive downlink assignment or uplink grantsfrom the base station for the second BWP. The UE may transmit or receivetransport blocks via the second BWP.

FIG. 29 shows an example of the embodiment. In an example, a UE (e.g.,UE in FIG. 29) may receive from a base station (e.g., Base Station inFIG. 29), one or more RRC messages comprising first configurationparameters of a plurality of BWPs and second configuration parameters ofreference signals (RSs). The first configuration parameters may comprisea timer value for a BWP inactivity timer. The plurality of BWPs maycomprise a first BWP and a default BWP. The second configurationparameters may comprise: one or more radio resource configurationparameters of a plurality of RSs; a report quantity indicator; one ormore uplink control channel parameters. The UE may receive a downlinkcontrol information indicating switching to the first BWP as an activeBWP. In response to the downlink control information, the UE mayactivate the first BWP, start the BWP inactivity timer with the timervalue, and/or monitor a downlink control channel on the first BWP. In anexample, after activating the first BWP, the UE may transmit one or morebeam reports for the first BWP. The one or more beam reports maycomprise one or more RSRP reports based on the plurality of RSs. The oneor more RSRP reports may comprise at least a RS index indicating one ofthe plurality of RSs and a RSRP value for the one of the plurality ofRSs.

In an example, a UE may receive a radio resource control messagecomprising configuration parameters of a cell, the configurationparameters comprising at least one of: first bandwidth part (BWP)configuration parameters for a first BWP; and second BWP configurationparameters for a default BWP. The UE may activate the first BWP. The UEmay determine that a parameter for a BWP inactivity timer is absent fromthe configuration parameters. In response to the determining, the UE maydisable the BWP inactivity timer of the first BWP without switching tothe default BWP. The UE may maintain, in response to disabling the BWPinactivity timer, the first BWP as an active BWP until the wirelessdevice receives a command indicating a BWP switching.

In an example, a UE may receive a first radio resource control messagecomprising first configuration parameters of a cell, the firstconfiguration parameters comprising: first bandwidth part (BWP)configuration parameters for a default BWP; second BWP configurationparameters a first BWP; and a parameter for a BWP inactivity timer. TheUE may start the BWP inactivity timer in response to activating thefirst BWP. The UE may receive a second radio resource control messagecomprising second configuration parameters of the cell. The UE maydetermine that the timer parameter for the BWP inactivity timer isabsent in the second configuration parameters. In response to thedetermining, the UE may disable the BWP inactivity timer. The UE maymaintain the first BWP as an active BWP in response to disabling the BWPinactivity timer. The UE may maintain the first BWP as the active BWPuntil the UE receives a command indicating a BWP switching.

In an example, a UE may receive a first radio resource control (RRC)message comprising first configuration parameters of a cell, the firstconfiguration parameters indicating: one or more bandwidth parts (BWPs)comprising a default BWP and/or an initial active BWP; and a valueassociated with a BWP inactivity timer. The UE may receive a downlinkcontrol information indicating downlink assignments or uplink grant on aBWP of the one or more BWPs. The UE may start the BWP timer with thevalue in response to the downlink control information. The UE mayreceive a second radio resource control message comprising secondconfiguration parameters of the cell, wherein the value associated withthe BWP timer is set to infinite. In response to the secondconfiguration parameters, the UE may disable the BWP inactivity timer.The UE may maintain the first BWP as an active BWP in response todisabling the BWP inactivity timer. The UE may maintain the first BWP asthe active BWP until the UE receives a command indicating a BWPswitching.

In an example, a UE may receive from a base station, one or more radioresource control messages comprising configuration parameters of a cell,the configuration parameters comprising first radio resource parametersof bandwidth parts (BWPs) comprising a first BWP and second radioresource parameters of reference signals. The UE may receive a downlinkcontrol information indicating switching to the first BWP as an activeBWP. The UE may activate the first BWP in response to the downlinkcontrol information. The UE may transmit, in response to activating thefirst BWP, one or more reference signal received power (RSRP) reportsfor the first BWP, wherein the one or more RSRP reports comprise areference signal index indicating one of the reference signals. Thereference signals may comprise one or more channel state informationreference signals and/or one or more synchronization signal blocks.

In an example, a UE may activate a first bandwidth part in response toswitching to the first bandwidth part as an active bandwidth part. TheUE may transmit, in response to the activating the first bandwidth part,one or more reference signal received power reports for the firstbandwidth part. The one or more reference signal received power reportsmay comprise a reference signal index indicating reference signals and avalue of reference signal received power of the reference signals.

In an example, a base station may configure a wireless device withuplink transmission without grant. The resources for uplink transmissionscheme without grant may be semi-statically (re-)configured. In anexample, the resource configuration may at least comprise physicalresources in time and frequency domain and RS parameters. Theconfiguration parameters may comprise at least modulation and codingscheme (MCS) and/or redundancy version and/or a number of repetitions(K). In an example, a wireless device may be configured with multiple Kvalues. For an uplink transmission without grant, RS may be transmittedwith data. In an example, the same channel structure as grant-basedtransmission may be employed for uplink transmission without grant. Inan example, at least for CP-OFDM, a common DMRS structure may be usedfor downlink and uplink. In an example, for am uplink transmission withand/or without grant, K repetitions, including initial transmission,with/without same RV and with/without same MCS for the same transportblock may be employed. In an example, frequency hopping may be employedbetween initial transmission and a retransmission and/or betweenretransmissions. In an example, for uplink transmission without grant, awireless device may continue repetitions for a TB until either anacknowledgement (ACK) is successfully received from a base station orthe number of repetitions for the TB reaches K. In an example, for awireless device configured with K repetitions for a TB transmission withand/or without grant, the wireless device may continue repetition forthe TB until an uplink grant is successfully received for aslot/mini-slot for the same TB and/or an acknowledgement/indication ofsuccessful receiving of that TB from base station and/or the number ofrepetitions for that TB reaches K. In an example, a wireless device maybe identified based on or a wireless device ID may be based on RSsequence/configuration for the wireless device and/or radio resourcesconfigured for uplink transmission.

In an example, time and frequency resource for uplink transmissionwithout grant may be configured in a wireless device-specific manner.The network may configure the same time/frequency resource and/or RSparameters to multiple wireless devices. The base station may avoidcollision with network implementation. The base station may identify awireless device ID based on physical layer parameters such astime/frequency resources and/or RS (e.g., DMRS) resources/parameters. Inan example, both DFT-S-OFDM and CP-OFDM may be supported for uplinktransmission without grant. In an example, uplink transmission withoutgrant may support one or more HARQ processes. HARQ process ID may beidentified based on resources used for uplink transmission withoutgrant, e.g., time/frequency resources and/or RS parameters for HARQprocess ID identification for both transmission with and without grant.

In an example, a wireless device may be configured with a plurality ofparameters for uplink data transmission without grant. In an example, awireless device may be configured with reference symbol, time andfrequency resources in a wireless device-specific manner. The time andfrequency resources configured for a wireless device may or may notcollide with those of another wireless device. In an example, DFT-S-OFDMand CP-OFDM may be supported for uplink transmission without grant. Inan example, uplink transmission without grant may support a plurality ofHARQ processes. In an example, L1 signaling may be employed foractivation/deactivation of uplink transmission without grant. In anexample, L1 signaling may be used for modification of parametersconfigured by RRC. Example parameters may comprise time domain resourceallocation (e.g., for one transmission), frequency domain resourceallocation (e.g., in terms of RBs or RBGs), wireless device-specificDMRS configuration, MCS/TBS, etc. In an example, L1 signaling may beused for switching to grant-based re-transmission for the same TB. In anexample, the L1 signaling may be based on wireless device-specific DCI(e.g., uplink grant) or a group common DCI. In an example, RRC(re-)configuration of a set of resource and parameters may comprisetransmission interval, physical resource such as time domain resourceallocation (e.g., for one transmission), frequency domain resourceallocation, e.g., in terms of RBs or RBG(s), wireless device-specificDMRS configuration, etc. In an example, a plurality of physicalresources may be configured in the transmission interval. In an example,one or more repetitions of a same one or more TBs may be performed(e.g., during the transmission interval) after an initial transmission.In an example, a repetition in the one or more repetitions may beperformed in the same resource employed for initial transmission. In anexample, a repetition in the one or more repetitions may be may be in adifferent resource than the initial transmission. The radio resourcesemployed for initial transmission and repetition may or may not betimely contiguous.

In an example, uplink transmission without grant, may beconfigured/activated with a plurality of types. In an example firsttype, UL data transmission without grant may be activated/deactivatedbased on RRC (re-)configuration without L1 signaling. In an examplesecond type, UL data transmission without grant may be based on both RRCconfiguration and L1 signaling for activation/deactivation. In anexample third type, UL data transmission without grant may be based onRRC configuration and may allow L1 signaling to modify some parametersconfigured by RRC. In an example, for first type UL data transmissionwithout grant, the RRC (re-) configuration may comprise periodicity andoffset of a resource with respect to SFN=0, time domain resourceallocation, frequency domain resource allocation, wirelessdevice-specific DMRS configuration, MCS/TBS, number of repetitions K,power control related parameters, HARQ related parameters, etc. In anexample, for second type UL transmission without grant, some ofparameters, for example, periodicity and power control relatedparameters, may be RRC configured. In an example, for second type ULtransmission without grant, the parameters not RRC configured and/orrequired to be updated, for example an offset value with respect to atiming reference, time domain resource allocation, frequency domainresource allocation, wireless device-specific DMRS configuration, and/orMCS/TBS, may be indicated by L1 signaling. The number of repetitions Kmay be RRC configured and/or indicated by L1 signaling.

In an example, an uplink grant, a group-common DCI, and/or HARQ feedbackindication mechanism employed for an uplink transmission without grantmay indicate an ACK or NACK implicitly or explicitly to reduce asignaling overhead and thereby to fulfill one or more servicerequirements (e.g., URLLC).

In an example, an uplink grant in response to an uplink transmissionwithout grant may indicate an ACK for the uplink transmission withoutgrant. The uplink grant may be a dynamic grant, e.g., for the same HARQprocess as the uplink transmission without grant. In an example, anuplink grant for a new data transmission may implicitly indicate an ACKfor an uplink transmission without grant. In an example, an uplink grantfor the same TB initially transmitted without grant may indicate NACKfor an uplink transmission without grant.

In an example, a group-common DCI may be employed to indicate one ormore HARQ feedbacks of one or more wireless devices for uplinktransmission without grant. In an example, the group common DCI mayindicate ACK. In an example, the group common DCI may indicate NACK. Inan example, the group common DCI may indicate ACK and NACK.

In an example, the wireless device may employ a timer to determine animplicit and/or explicit HARQ feedback (ACK/NACK) corresponding to anuplink transmission without grant. In an example, the timer value may beconfigured for the wireless device via RRC. The wireless device mayreceive one or more RRC message indicating the timer value. In anexample, the wireless device may (re-) start the timer in response to anuplink transmission without grant (e.g., one or more TBs correspondingto an uplink transmission without grant). In an example, the wirelessdevice may assume an ACK in response to the timer expiring and notreceiving a NACK after K repetitions. In an example, the wireless devicemay assume a NACK in response to the timer expiring and not receiving anACK. In an example, the wireless device may assume a NACK correspondingto an uplink transmission without grant in response to receiving a grant(e.g., dynamic grant) for retransmission of the same one or more TBs ina first uplink transmission without grant (e.g., the same HARQ processand with NDI not toggled). In an example, the wireless device may assumea NACK corresponding to an uplink transmission without grant in responseto receiving a grant (e.g., dynamic grant) for retransmission of thesame one or more TB in a first uplink transmission without grant in aperiod of time. In an example, the period of time may be configured forthe wireless device. The wireless device may receive an RRC messageindicating the period of time. In an example, the period of time may bepre-configured. In an example, the period of time may be indicatedand/or updated by L1 signaling.

In an example embodiment, a base station may configure a wireless devicewith one or more RNTIs for uplink transmission without grant. In anexample, the base station may configure a RNIT for uplink transmissionwithout grant per configuration, per service, per type (e.g., the first,second, and/or third types) and/or per a wireless device.

In an example embodiment, a base station may configure a wireless devicewith a first RNTI. The first RNTI may be a group-common RNTI. In anexample, for indicating HARQ feedback (e.g., ACK/NACK) corresponding toone or more uplink transmissions (e.g., one or more TBs corresponding toone or more uplink transmission) without uplink grant (e.g., forsemi-persistent scheduling (SPS) and/or grant-free resourceconfiguration) for one or more wireless devices, the base station maytransmit a downlink control information (DCI) (e.g., a group common DCI)corresponding to the first RNTI. The DCI may be scrambled based on thefirst RNTI. In an example, a wireless device may monitor a common searchspace to detect the DCI corresponding to the first RNTI. In an example,the base station may transmit/indicate NACK (e.g., using the DCI)corresponding to one or more TBs of the wireless device and the wirelessdevice may assume an ACK (e.g., implicit ACK) if no NACK is receivedwithin a period of time. In an example, the base station maytransmit/indicate an ACK (e.g., using the DCI) and the wireless devicemay assume a NACK (e.g., implicit NACK) if no ACK is received within aperiod of time. The period for time may be configured for the wirelessdevice. In an example, the base station may transmit an RRC messageindicating the period of time. In an example, the period of time may bepre-configured. In an example, the wireless device may transmit up to afirst number of repetitions of a same one or more TBs corresponding toan uplink transmission without grant. The period of time may be or maynot be based on the duration that the first number of repetitions of thesame one or more TBs corresponding to the uplink transmission isreceived. The wireless device may monitor for the DCI at least for aportion of the period of time. The wireless device may stop monitoringthe DCI in response to receiving the ACK/NACK corresponding to theuplink transmission without grant. In an example, the DCI may compriseACK/NACK for a plurality of wireless devices. The plurality of wirelessdevices may be configured with the same first RNTI used for transmissionof the DCI. In an example, the plurality of wireless devices configuredwith the same first RNTI may monitor the search space and may detect thesame DCI and may identify HARQ feedback corresponding to theirtransmissions. In an example, the DCI may comprise a plurality of HARQfeedbacks (e.g., corresponding to a plurality of TBs) for the samewireless device. The mapping between a HARQ feedback and a correspondingwireless device and/or a TB in a plurality of TBs transmitted by awireless device may be based on a rule and/or implicitly/explicitlyindicated by the DCI.

Uplink demodulation reference signals (DMRS) may be used for channelestimation and/or coherent demodulation of PUSCH and PUCCH. In anexample, a base station may configure a wireless device with DMRSconfiguration parameters. The wireless device may receive one or moreRRC messages. The one or more RRC messages may comprise a DMRS-ConfigIE. The DMRS-Config IE may comprise DMRS configuration parameters. Anexample, DMRS-Config IE may be as follows. Example embodiments mayenhance the DMRS-Config configuration and/or the DMRS-Configconfiguration parameters.

DMRS-Config ::= CHOICE {  release   NULL,  setup   SEQUENCE {  scramblingIdentity   INTEGER (0..503),   scramblingIdentity2   INTEGER (0..503)  } } DMRS-Config ::=  SEQUENCE {   dmrs-tableAlt   ENUMERATED {true} OPTIONAL -- Need OR }

In an example, parameters scramblingIdentity and/or scramblingIdentity2may indicate a parameter n^(DMRS,i) _(ID). In an example, the parameter,dmrs-tableAlt may indicate whether to use an alternative table for DMRSupon PDSCH transmission.

Example embodiments of the disclosure may support an uplink (UL)transmission without an UL grant, referred to as a grant-free (GF) ULtransmission or a configured grant Type 1, for one or more servicetypes, e.g., URLLC. In an example, a base station may transmit one ormore messages (e.g., RRC messages) comprising configuration parametersof the GF UL transmission. For example, the configuration parameters mayindicate one or more resources (e.g., may be referred to as one or moreGF UL radio resources). For example, the configuration parameters mayindicate time and frequency location of the one or more GF UL radioresources. For example, the time and frequency location may be indicatedbased on a time offset and/or frequency offset. For example, the timeoffset may be defined in terms of a first system frame number, a firstsubframe number, a first slot number, a first OFDM symbol number, and/orcombination thereof. For example, the time offset may comprise one ormore times offsets, for example, a first offset in terms of a firstsystem frame number and/or a second offset in terms of a first subframenumber, a first slot number, and/or a first OFDM symbol number withrespect to the first offset. For example, the first offset may be zerothat may indicate the system frame number zero. For example, thefrequency location may be indicated by a frequency offset. For example,the frequency offset may be defined with respect to a frequencyreference. For example, the frequency reference may be a centerfrequency. For example, the frequency reference may be a first frequencyof an operating bandwidth. For example, the first frequency may be alowest frequency of an operating bandwidth. For example, the firstfrequency may be a highest frequency of an operating bandwidth. Forexample, the first frequency may be a fourth frequency that may bepredefined, configured by a base station, and/or indicated by a basestation. For example, the frequency reference may be a second frequencyof an operating bandwidth part. For example, the second frequency may bea lowest frequency of an operating bandwidth part. For example, thesecond frequency may be a highest frequency of an operating bandwidthpart. For example, the second frequency may be a fourth frequency thatmay be predefined, configured by a base station, and/or indicated by abase station.

In an example, one or more GF (configured grant) UL radio resources maybe periodic resources. For example, the configuration parameters mayindicate a periodicity of the one or more GF UL radio resources. Forexample, the wireless device configured by the base station with the GFUL radio resources may transmit one or more data packets via the GF ULradio resources without receiving a dynamic UL grant, which may resultin reducing the signaling overhead comparing with a GB UL transmission.Such a service type that has strict requirements, for example in termsof latency and reliability such as URLLC, may be a candidate for which abase station may configure a wireless device with the GF ULtransmission. The wireless device configured with the GF UL radioresource may skip an UL transmission on the GF UL radio resource ifthere is no data to transmit.

In example embodiments, the GF UL transmission may support multiplewireless devices to access the same GF UL radio resources, may referredto as GF radio resource pool, in order to achieve lower latency andlower signaling overhead. A GF radio resource pool may be defined as asubset of one or more radio resources from a common radio resource set(e.g. from all uplink shared channel radio resources). The GF radioresource pool may be employed to allocate exclusive or partiallyoverlapped one or more radio resources for GF UL transmissions in a cellor to organize frequency/time reuse between different cells or parts ofa cell (e.g. cell-center and cell-edge).

In example embodiments, if a base station configures multiple wirelessdevices with the same (or partially overlapped) GF radio resource pool,there may be a collision between the GF UL transmissions of two or morewireless devices. The base station may configure one or more parametersto assign a wireless device specific demodulation reference signal(DMRS) along with the GF radio resource pool configuration in order toidentify a wireless device ID. In an example, the one or more parametersmay indicate at least one of a root index of a set of Zadoff-Chu (ZC)sequences, a cyclic shift (CS) index, a TDM/FDM pattern index, or anorthogonal cover code (OCC) sequences or index.

In example embodiments, for the wireless device ID identification, abase station may employ one or more preamble sequences that may betransmitted together with the PUSCH data. The one or more preamblesequences may be designed to be reliable enough and to meet thedetection requirement of a service, e.g., URLLC. For wireless devicesconfigured with a GF radio resource pool, a preamble sequence may beuniquely allocated to a wireless device. A base station may configuredifferent GF radio resources for different sets of wireless devices suchthat the preamble sequences may be reused in different GF radioresources. To have reliable detection performance, the preamblesequences may be mutually orthogonal, e.g. orthogonality between ZC rootsequences with different cyclic shifts. In an example, a wireless devicemay transmit one or more preambles together with the data block in thefirst step and receive a response in the second step. The data may berepeated K times depending on a base station configuration. The one ormore preambles may not be repeated. The response from a base station maybe an UL grant or a dedicated ACK/NACK transmitted in the form of adownlink control information (DCI).

In an example, a grant-free (GF) resource pool configuration may not beknown to wireless devices. It may be coordinated between different cellsfor interference coordination. If the GF resource pools are known towireless devices, those may be semi-statically configured by wirelessdevice-specific RRC signaling or non-UE-specific RRC signaling (e.g.,via broadcasting a system information block in LTE). The RRC signalingfor GF radio resource configuration may comprise one or more parametersindicating at least one of following: periodicity and offset of aresource with respect to SFN=0, time domain resource allocation,frequency domain resource allocation, wireless device-specific DMRSconfiguration, a modulation and coding scheme (MCS), a transport blocksize (TBS), number of repetitions K, a hopping pattern, HARQ relatedparameters, or power control related parameters. A wireless device mayactivate the GF UL transmission configured by the RRC signaling inresponse to receiving the RRC signaling without an additional signaling.

In an example, an L1 activation signaling may be employed with RRCsignaling to configure/activate a GF configuration. In an example, RRCsignaling may configure one or more parameters of GF UL transmission tothe wireless device, and L1 activation signaling may activate, ordeactivate the configured GF UL transmission. L1 activation signalingmay be used to configure, adjust, modify, or update one or moreparameters associated with GF UL transmission.

The L1 activation signaling may be transmitted via a PDCCH in the formof DCI, e.g., DCI employed for LTE UL semi-persistent scheduling (SPS).base station may assign a radio network temporary identifier (RNTI) fora wireless device along with GF configuration parameters in the RRCsignaling. With the assigned RNTI, wireless device may monitor the PDCCHto receive the L1 activation signaling masked by the RNTI.

In an example, the RRC (re-)configuration of GF UL transmission withoutUL grant may comprise at least one of following: Periodicity of aresource or Power control related parameters. The L1 activationsignaling may provide at least one of the following parameters for theGF resource: Offset associated with the periodicity with respect to atiming reference, time domain resource allocation, frequency domainresource allocation, wireless device-specific DMRS configuration, anMCS/TBS value, HARQ related parameters, number of repetitions K, or ahopping pattern.

In an example, the MCS may be indicated by the wireless device withinthe grant-free data. In an example, in order to avoid the blind decodingof MCS indication, the limited number of MCS levels may bepre-configured by a base station, e.g., K bits may be used to indicateMCS of grant-free data, where K may be as small as possible. The numberof REs used to transmit MCS indication in a resource group may besemi-statically configured. In the GF operation, there may be one commonMCS predefined for all wireless devices. In this case, there may be atradeoff between a spectrum efficiency and decoding reliability, e.g.,the spectrum efficiency may be reduced if a low level of MCS is used,while the data transmission reliability gets higher. The NR maypredefine a mapping rule between multiple time/frequency resources forUL grant-free transmission and MCSs. In an example, a wireless devicemay select an appropriate MCS according to a DL measurement andassociated time/frequency resources to transmit UL data. In this way,wireless device may choose a MCS based on the channel status andincrease the resource utilization.

In an example, when a wireless device configured with a GF ULtransmission, the GF UL transmission may be activated in different ways,via RRC signaling, via L1 activation signaling, or combination thereof.The need for L1 activation signaling may depend on service types, andthe dynamic activation (e.g., activation via L1 activation signaling)may not be supported in the NR or may be configurable based on serviceand traffic considerations.

In example, it may be up to a base station whether to configure awireless device with or without L1 activation signaling, which may bedetermined based on, for example, traffic pattern, latency requirements,and other possible aspects. With the L1 activation signaling, a wirelessdevice may transmit a data packet with the configured time frequencyradio resource when the wireless device receives an L1 activationsignaling from the base station. If the L1 activation signaling is notconfigured, a wireless device may start an UL transmission with theconfigured GF radio resource at any moment or in a certain time interval(which may be configured by RRC signaling or pre-defined) once theconfiguration is completed. For example, a wireless device may activatethe GF UL transmission in response to receiving the RRC signalingconfiguring the GF UL transmission. In an example, the activation type(via RRC signaling or via L1 activation signaling) may bepre-configured.

In an example, RRC signaling, transmitted from a base station to awireless device to configure an UL GF transmission, may comprise anindicator employed for indicating whether the activation of the UL GFtransmission needs an L1 activation signaling. If the indicatorindicates a need of L1 activation signaling, the wireless device maywait an L1 activation signaling and activate the configured UL GFtransmission in response to receiving the L1 activation signaling. Whenthe L1 activation signaling is employed, the wireless device maytransmit an acknowledgement in response to receiving an L1 activationsignaling to the base station to inform of whether the wireless devicecorrectly receives it.

In an example, if the indicator indicates no need of L1 activationsignaling, the UL GF transmission may be activated in response to theRRC signaling configuring the GF UL transmission. For the case of theactivation of GF UL transmission without the L1 activation signaling,the wireless device may not determine when to start the GF ULtransmission. The base station and wireless device may predefine thestart timing based on a time offset and the transmission time interval(TTI), e.g., a subframe, slot, or mini-slot, where the wireless devicereceive the RRC signaling for the GF UL transmission configuration, orthe RRC configuration may comprise one or more parameters indicating thestart timing (in terms of a subframe, slot, or mini-slot).

In an example, RRC signaling may not comprise an indicator whether theactivation needs a L1 activation signaling. A wireless device mayimplicitly know whether the configured GF transmission is activated byRRC signaling or L1 activation signaling based on a format of RRCconfiguration for GF UL transmission. For example, for a GF ULtransmission without L1 activation signaling, the RRC signaling forconfiguring and activating the GF UL transmission may comprise one ormore parameters for the UL GF transmission. For a GF UL transmissionactivated by the L1 activation signaling, a RRC signaling may comprise adifferent number of parameters that may be less than a number ofparameters in the RRC signaling activating the GF UL transmission. Inthis case, the absence and/or presence of one or more parameters (or thenumber of parameters) in the RRC signaling may be an implicit indicatorfor a wireless device to identify whether to activate the GF ULtransmission via RRC signaling or via L1 activation signaling.

In an example, the L1 activation signaling may comprise one or moreparameters indicating at least one of GF configuration, e.g., starttiming of GF UL transmission, GF time and frequency radio resources,DMRS parameters, a modulation and coding scheme (MCS), a transport blocksize (TBS), number of repetitions K, a hopping pattern, or power controlparameters. For example, a downlink control information (DCI) formatused for the activation of the GF UL transmission may comprise one ormore fields indicating a MCS for the GF UL transmission. In this case,the GF UL transmission requiring the L1 activation signaling may beconfigured with a RRC signaling that may not comprise one or moreparameters indicating the MCS for the GF UL transmission. The MCSinformation may be carried by a L1 signaling which activate the GF ULtransmission. If a wireless device receives a RRC signaling comprising aMCS for a GF UL transmission, the wireless device may activate the GF ULtransmission in response to the RRC signaling without waiting for a L1signaling.

In an example, if the service does not require high reliability andlatency, the L1 activation signaling may be configured to controlnetwork resource load and utilization. For a delay sensitive service,the additional activation signaling may cause additional delay and maylead to potential service interruption or unavailability for the periodof applying and requesting the activation. In this case, a base stationmay configure the wireless device with a GF UL transmission such thatthe GF UL transmission is activated in response to the RRC signalingcomprising a GF radio resource configuration and transmissionparameters.

In an example, there may be a case that the GF radio resource isover-allocated which may result in the waste of radio resources with fewwireless devices. In this case, L1 signaling may be used to reconfigurethe GF UL radio resource or one or more GF transmission parameters. Byallowing L1 signaling-based reconfiguration, wireless devices mayperiodically monitor downlink control channel to detect the L1 signalingscrambled by a RNTI that may indicate whether the configured GF radioresources or parameters are changed. This may increase the powerconsumption of wireless device, and the periodicity to check thedownlink control signaling may need to be configurable. In an example,if a radio resource utilization is important, the periodicity may beconfigured to be short like every 1 minute or every radio frame. If thepower consumption is important, the periodicity may be configured to belong like every 1 hour. The periodicity to check downlink controlsignaling may need to be allowed to be separated from the periodicity ofGF UL transmission, e.g., in order to shorten the latency. In anexample, the periodicity of GF radio resource may be less than 1 ms like0.125 ms but the periodicity to check downlink control signaling may be1 minute or 1 hour. In an example, for deactivating the activated GFoperation, L1 deactivation signaling may be used for all services inorder to release resources as fast as possible.

For the GF UL transmission, a base station may support a K-repetition ofthe same transport block (TB) transmission over the GF radio resourcepool until one or more conditions are met. The wireless device maycontinue the repetitions up to K times for the same TB until one of thefollowing conditions is met: If an UL grant (or HARQ ACK/NACK) issuccessfully received from the base station before the number ofrepetitions reaches K, the number of repetitions for the TB reaches K,or other termination condition of repetition may apply.

In an example, the number of repetitions, K, may be a configurableparameter that may be wireless device-specific, and/or cell-specific. Amini-slot or a symbol may be a unit of the K-repetition. A base stationmay configure the number of this repetition and the radio resource inadvance via one or more RRC messages. The base station may transmit L1activation signaling comprising a parameter indicating the number ofrepetitions K. The base station may assume a set of initial transmissionand the repetition as one amount of the transmission. The base stationmay not be required to prepare the case of only initial transmission oronly repetition. One may call the set of initial transmission and itsone or more repetitions as an extended TTI. The repetitions may not benecessarily contiguous in time. If the repetitions are contiguous intime, it may allow coherent combining. If the repetitions are notcontiguous in time, it may allow time diversity.

In an example, when the GF UL transmission of two wireless devicescollides in the same GF radio resource pool, a base station may fail todetect both wireless devices' data. When the two wireless devicesretransmit the data without UL grants, the two wireless devices maycollide again. In such a case, hopping may to solve the collisionproblem when radio resources are shared by multiple wireless devices.The hopping may randomize the collision relationship between wirelessdevices within a certain time interval to avoid persistent collision. Itmay bring a diversity gain on the frequency domain. A wirelessdevice-specific hopping pattern may be pre-configured or be indicated byRRC signaling or L1 activation signaling. The wireless device-specifichopping pattern may be generated based on a known wirelessdevice-specific ID, e.g., wireless device-specific DMRS index and/orRNTI.

There may be many factors considered for the hopping pattern design,such as the number of resource units (RUs), the max number of wirelessdevices sharing the same RU, the recently used RU index, the recenthopping index or the current slot index, the information indicatingrecently used sequence, hopping pattern, or hopping rule. The sequencedescribed above may be a DMRS, a spreading sequence, or a preamblesequence that may be wireless device-specific.

In an example, the repetitions parameter K may be configured by one ormore RRC messages, L1 activation signaling, or combination thereof. Awireless device configured with the repetitions parameter K may transmita transport block (TB) K times. The wireless device may transmit the TBK times with the same redundancy version (RV) or transmit the TB K timeswith different RVs between the repetition. For example, the RVdetermination for K repetitions may comprise the initial transmission.

In an example, for the case that the GF UL transmission is activated byone or more RRC messages, the RV determination may be fixed to apre-defined single value or fixed to a pre-defined RV pattern comprisinga plurality of RVs. In an example, the RV determination may beconfigured by the one or more RRC messages with a single value or a RVpattern comprising a plurality of RVs.

In an example, for the case that the GF UL transmission is (fully orpartially) configured by one or more RRC messages and activated by an L1activation signaling, the RV determination may be fixed to a singlevalue or fixed to a pre-defined RV pattern comprising a plurality ofRVs. For the case that the GF UL transmission is (fully or partially)configured by one or more RRC messages and activated by L1 activationsignaling, the RV determination may be configured by the one or more RRCmessages with a single value or a RV pattern comprising a plurality ofRVs. For the case that the GF UL transmission is (fully or partially)configured by one or more RRC messages and activated by L1 activationsignaling, the RV determination may be configured by the L1 activationsignaling with a single value or fixed to a RV pattern comprising aplurality of RVs.

In example embodiments, the base station may support to switch betweenGF and GB UL transmissions to balance resource utilization anddelay/reliability requirements of associated services. The GF ULtransmission may be based on a semi-static resource configuration thatmay be beneficial to reduce latency. Such a pre-defined resourceconfiguration may be hard to satisfy all potential services or packetsizes. The overhead may be large, and the packet size for a service,such as URLLC, may be variable. If a wireless device's data packetcollides with other wireless device's packets in the GF UL transmission,a re-attempt to access GF radio resources may not achieve the servicerequirements. In such cases, switching from GF to GB UL transmissionsmay be beneficial.

In example embodiments, to support the switching between GF and GB ULtransmissions, the initial transmission on the pre-configured GF radioresources may include wireless device identification (ID), for example,explicit wireless device ID information (e.g. C-RNTI) or implicitwireless device information such as a DMRS cyclic shift (assuming use ofZC sequences) specific signature. To inform a base station of whetherthe wireless device has remaining data to transmit, the wireless devicemay include buffer status reporting (BSR) with the initial datatransmission. If a base station successfully decodes data transmitted bya wireless device and determines that the wireless device has remainingdata to transmit (e.g. from a BSR report), the base station may switch atype of scheduling for wireless device from GF to GB UL transmissions.If a base station fails to decode data transmitted by the wirelessdevice but successfully detects the wireless device ID from the uniquelyassigned sequence (e.g., preamble and/or DMRS), the base station mayswitch a type of scheduling for wireless device from GF to GB ULtransmissions. The UL grant for subsequent data transmissions may bewith CRC scrambled by the wireless device's RNTI (may be determinedeither by explicit signaling in the initial transmission or implicitlyby the DMRS cyclic shift).

In example embodiments, one of the termination conditions for theK-repetitions may be a reception of a DCI comprising an UL grant whichschedules an UL (re)transmission for the same TB. A base station mayassign dedicated resources for retransmission in order to ensure the TBto be delivered within the latency budget. This behavior may beclassified as scheduling switching from GF to GB operation. In thiscase, a wireless device may need to link the received grant with thetransmitted TB in order to understand which TB to be retransmitted incase there are multiple ongoing transmission processes at the wirelessdevice. For these purposes, the wireless device and base station mayhave the same notion of TB (and/or RV) counting.

In example embodiments, for the GF operation, the TB counting may not bepossible if a base station may not detect one or more TBs due tocollisions. In order to make an association between a DCI with a TB,there may be one or more options. If there is no other transmissionprocess at the wireless device side, it may directly associate the DCIwith a TB which is being transmitted. If there are at least twodifferent TBs, a wireless device may deduct that the DCI is for aparticular TB by applying an implicit linkage assuming only one TB istransmitted in one transmission interval. In this case, if the intervalbetween detected wireless device transmission and a grant is fixed, itmay unambiguously determine which TB may be retransmitted. If the timingbetween a detected transmission and a retransmission grant is notpreconfigured, an explicit indication of the retransmitted TB may becarried by DCI. If a wireless device detects that a grant for one TBoverlaps with transmission of another ongoing TB, the wireless devicemay assume precedence of the grant comparing to the grant-freeretransmissions. If a grant is received for a new TB (e.g. for aperiodicCSI reporting) and overlaps with the GF UL transmissions, the GFtransmissions may be dropped in the resources. Alternatively, aprioritization rule whether to transmit a triggered report or GF datamay be introduced depending on priority of the associated services. Forexample, if URLLC services is assumed, then the CSI reporting may bedropped in this example.

An example embodiment may employ a dedicated pre-assigned channel forearly termination. For example, the physical HARQ indicator channel(PHICH) defined in LTE may be employed as an acknowledge indicator. InLTE, the PHICH for a wireless device may be determined based on thephysical resource block (PRB) and cyclic shift of the DMRS correspondingto the wireless device's PUSCH transmission. Similar design principlemay be employed for a GF UL transmission. The early termination based onPHICH-like channel may improve the control channel capacity and systemcapacity. If a base station has successfully received a TB, the basestation may obtain the corresponding information about the transmissionof the TB, such as the wireless device ID, the resource employed forcarrying this transmission, the DMRS employed for this transmission. Thephysical resources may be shared among multiple wireless devices who mayhave their own unique identifiers (e.g., DMRS) used in the GF radioresource pool. Therefore, even for GF UL transmission, if the basestation has successfully received a TB, a unique PHICH may bedetermined.

In example embodiments, using a sequence based signal may be used forearly termination of K-repetition. In this case, a sequence based signalmay be transmitted via one or more pre-assigned channels to inform thewireless device to terminate the repetition of transmission. In thiscase, the signal may be transmitted when a base station successfullydecodes a TB. The wireless device may perform a simple signal detectionfor the presence or absence to decide whether to continue therepetitions or not.

In example embodiments, a base station may switch from GF to GB ULtransmissions in order to improve a GF radio resource shortage. In anexample, one or more wireless devices whose delay requirements are notstrict (e.g., comparing with URLLC requirements) may employ the GF radioresource to transmit a data packet. A base station may measure a levelof congestion of the GF UL radio resource shared by a plurality ofwireless devices based on statistics, e.g., resource utilization, load,and/or a number of wireless devices sharing the GF UL radio resource andset up a threshold policy to dynamically balance load or resourceutilization of the GF UL radio resource. If the resource usage statisticof the GF UL radio resource exceeds the predefined threshold, it may bebeneficial to switch some wireless devices from the GF UL radio resourceto the GB UL radio resource, which may result in decreasing the resourcecollision.

For example, a configured grant (Type 1 and/or Type 2) may be activatedon an active UL BWP to support a data transmission requiring a lowlatency (e.g., URLLC data packet). A wireless device and/or a basestation may not predict when a data packet arrives. When the data packetarrives, if a wireless device does not have an UL grant, the wirelessdevice may transmit a SR to a base station to request an UL grant for atransmission of the data packet. In response to receiving the SR, thebase station may transmit a control message comprising an UL grant forthe data packet. For the case of data transmission requiring a lowlatency, the SR-based UL grant assignment may not satisfy a requirement.In this case the configured grant may help a wireless device and/or abase station such that the data packet may be transmitted withoutrequesting an UL grant.

In an example, a BWP inactivity timer may be (re)started in response toreceiving, by a wireless device, a DCI comprising a DL assignment or anUL grant. Restarting a BWP inactivity timer in response to receiving aDCI may be for a wireless device to perform a transmission or areception on a current active BWP. For example, a wireless device mayreceive a DCI comprising a DL assignment on a current DL BWP. A wirelessdevice may (re)start BWP inactivity timer to keep monitoring controlchannel(s) and/or data channel(s) (and/or receiving a PDCCH and/orPDSCH) of the current DL BWP. For example, a wireless device may receivea DCI comprising an UL grant. A wireless device may (re)start BWPinactivity timer to keep monitoring control channel(s) on the current DLBWP to receive (and/or detect) a DCI (e.g., feedback message)corresponding to an UL transmission performed based on the UL grant.

In an example, at least one configured grant may be activated on an ULBWP of a cell. In an example, a wireless device and base station may runa BWP inactivity timer, for example, in response to activating a DL BWPthat is not a default BWP. For example, running a BWP inactivity timer(e.g., a DL BWP inactivity timer) may impact an UL transmission on oneor more radio resources associated with the at least one configuredgrant. In existing legacy mechanisms, BWP switching in response to anexpiry of a BWP inactivity timer may result in a performance loss andinterruption in uplink transmissions. The performance loss may includean increase in latency to (re)activate resource(s) of a configuredgrant. For example, for a time-division-duplexing system, a DL BWPswitching in response to an expiry of a downlink BWP inactivity timermay result in a UL BWP switching. This may be a case that a DL BWP ispaired with a UL BWP. If a UL BWP, where a configured grant isactivated, is switched to a new UL BWP, a base station may activate asecond configured grant on the new UL BWP. For example, a base stationmay not configure a second configured grant on the new UL BWP. The basestation may transmit control message(s) (e.g., RRC, MAC CE, and/or DCI)to a wireless to configure and/or activate a second configured grant onthe new UL BWP. For example, in existing mechanisms, a base stationand/or wireless device may not be able to fulfill requirement(s) of alatency-sensitive service (e.g., URLLC) with a delay caused by a BWPswitching in response to an expiry of a BWP inactivity timer. There is aneed for an enhanced BWP inactivity timer management mechanism to reducedelay and increase continuity and efficiency of uplink transmission whenconfigured grant is implemented. Example embodiments implements animproved BWP inactivity timer management mechanism to reduce unnecessaryBWP switching when configured grants is implemented.

For a configured grant (Type 1 and/or Type 2), a DCI may not be neededto indicate a periodic resource of the configured grant. For example, ahigher layer control message may configure a periodic resource of aconfigured grant. A wireless device may transmit a data packet via theperiodic resource without receiving a DCI. For example, a wirelessdevice may transmit a data packet via the periodic resource without aDCI while a BWP inactivity timer is running. In existing mechanisms, theBWP inactivity timer is (re)started when a wireless device receives aDCI comprising a downlink assignment or an UL grant. Since an ULtransmission via a periodic resource of a configured grant (Type 1and/or Type 2) does not require a DCI indicating an UL grant, a wirelessdevice may not (re)start a BWP inactivity timer. In this case, an activeBWP may be switched before receiving a feedback message (e.g., a DCIindicating a NACK) which may cause errors in the base station reception.There is a need for an enhanced BWP inactivity timer managementmechanism to reduce error scenarios in uplink transmission whenconfigured grant is implemented. Example embodiments implements animproved BWP inactivity timer management mechanism to reduce errors dueto BWP switching.

In legacy mechanisms, switching a BWP (e.g., DL BWP) to a default BWP inresponse to an expiry of the BWP inactivity timer may happen during ULand/or DL transmissions via at least one configured grants, which maycause a failure of the UL and/or DL transmissions via the at least oneconfigured grant and may results in a delay due to a retransmissionprocess, e.g., via HARQ. For example, switching a BWP (e.g., DL BWP) toa default BWP in response to an expiry of the BWP inactivity timer mayrequire a certain period of time for switching to a new BWP (e.g.,retuning RF, measurement gap) during which a wireless device may nottransmit and/or receive a data packet to/from a base station. In anexample, For a latency-sensitive service, e.g., URLLC, carried by the atleast one configured grant, such a period of time fortransmission/switching may be a crucial factor to determine whether tomeet the service requirements. For example, a traffic carried by the atleast one configured grant may require low latency and/or ultra-highreliability, which may not be achieved in a default BWP, e.g., due to asize of narrow bandwidth of the default BWP and/or due to a slotduration of the default BWP. For example, a wireless device and a basestation may transmit/receive one or more signals before/after switchinga BWP, e.g., CSI-RS, SRS, and/or acknowledge signal to inform of successswitching and/or to obtain a channel state information on a switchedBWP, which may result in additional power consumption for a wirelessdevice. For example, a base station may active an UL BWP with configuredgrant Type 1 and/or Type 2 for one or more wireless device for loadbalancing purpose. For example, keeping one or more radio resourcesassociated with the at least one configured grant on an active BWP otherthan a default BWP be beneficial for reducing a potential collisionand/or for load balancing purpose if the active BWP may be wider thanthe default BWP. There may be a need for an enhanced BWP inactivitytimer management that keeps an active DL BWP with an activatedconfigured grant (Type 1 and/or Type 2) as active for a first period oftime. Example embodiments implements an improved BWP inactivity timermanagement mechanism to increase a duration that a downlink BWP remainsactive when a configured grant is configured.

In FIG. 30 and FIG. 31, a wireless device may receive at least onemessage comprising configuration parameters indicating periodicresources of a configured grant of an uplink bandwidth part and a timervalue of a bandwidth part inactivity timer of a downlink bandwidth part.The wireless device may start the bandwidth part inactivity timer inresponse to activating a downlink bandwidth part. The wireless devicemay restart the bandwidth part inactivity timer in response totransmitting one or more data packets via a first transmission intervalof a first resource of the periodic resources of the uplink bandwidthpart (without receiving an additional DCI for transmitting the one ormore data packets). Example embodiment provides an improved BWPinactivity timer management mechanism that may reduce unnecessary BWPswitching (when configured grants is implemented), may reduce errors dueto BWP switching, and may increase a duration that a downlink BWPremains active. In an example embodiment, the wireless device maintainsa BWP inactivity timer for the downlink bandwidth part when theconfigured grant is configured for an uplink BWP. The wireless devicemay enable a BWP inactivity timer for the downlink bandwidth part andmay maintain a BWP inactivity timer with a finite timer value. Thisenhanced BWP inactivity timer management may reduce the possibility ofBWP switching while enabling automatic timer based BWP switching for thedownlink part when there is no transmission activity or when theconfigured grant is released/deactivated.

In an example embodiment, an enhanced BWP inactivity timer managementmechanism uses uplink configured transmissions for restarting a BWPinactivity timer of a downlink BWP. A downlink BWP inactivity timer isrestarted based on uplink transmissions via configured grant in additionto being restarted based on receiving DCIs on the downlink BWP. Thisenhanced BWP inactivity timer management may reduce unnecessary BWPswitching (when configured grants is implemented), may reduce errors dueto BWP switching, and may increase a duration that a downlink BWPremains active. In an example, in response to an expiry of the bandwidthpart inactivity timer of the downlink BWP, the wireless device mayswitch from the downlink bandwidth part to a default bandwidth part asan active bandwidth part.

FIG. 30 is example diagram illustrating scenarios for (re)starting a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure. A wireless device may activate a uplink configured grant(e.g., Type 1 GF and/or Type 2 GF). For Type 1 GF, a wireless device mayactivate the Type 1 GF with a first time offset (may be predefinedand/or configured by an RRC) in response to receiving RRC message(s)comprising one or more configured grant parameters. For Type 2 GF, asshown in FIG. 30, a wireless device may activate the Type 2 GF with afirst time offset (may be predefined and/or configured by an RRC) inresponse to receiving a DCI indicating an activation indicator of theType 2 GF. The configuration parameters of the configured grant (Type 1and/or Type 2) may indicate periodic radio resource allocation (e.g., asshown in FIG. 30) with a periodicity. The wireless device may restart aBWP inactivity timer of a downlink BWP one or more times after an uplinkconfigured grant is activated without receiving a DCI after activation.For example, the wireless device may restart a BWP inactivity timer of adownlink BWP at a time based on at least one of periodic radio resourcesof the activated configured grant. For example, the wireless device may(re)start one or more times the BWP inactivity timer at one or moredifferent times based on periodic radio resources of the activatedconfigured grant. For example, each of the one or more different timesmay be within a time duration of at least one of periodic radioresources of the activated configured grant. For example, the wirelessdevice may transmit one or more UL data packet via the at least one ofperiodic radio resources of the activated configured grant.

FIG. 31 is an example diagram illustrating scenarios (re)starting a BWPinactivity timer of a downlink bandwidth part as per an aspect of anembodiment of the present disclosure. For example, a wireless device mayswitch an active BWP to a first BWP that is not a default BWP. There maybe one or more ways that the wireless device may switch the active BWP.For example, a base station may transmit, to a wireless device, acontrol message (e.g., RRC message, MAC CE and/or DCI) indicating theBWP switching to a first BWP. For example, the control message may causereconfiguration of BWP configuration parameters, e.g., the controlmessage may be RRC message(s). For example, the control message maycomprise downlink assignment and/or uplink grant, e.g., the controlmessage may be DCI. For example, if a first downlink BWP, that becomes anew active BWP, is not a default BWP, a wireless device may start a BWPinactivity timer in response to BWP switching to the first downlink BWP.While the first downlink BWP is being active (e.g., a BWP inactivitytimer is running), there may be one or more resources of one or moreconfigured uplink grants (Type 1 and/or Type 2) configured on an UL BWP.In an example, the one or more configured uplink grants may bepreconfigured before a first downlink BWP is activated. In an example,the one or more configured uplink grants may be configured after a firstBWP is activated.

FIG. 32A shows examples of a BWP inactivity timer management of a DL BWPthat may be performed by a base station. In FIG. 32A, at step 3210, abase station may transmit, to a wireless device, one or more RRCmessages comprising configuration parameters of one or more BWPs and/orone or more uplink configured grants. The base station may activate(and/or (re)initialize) at least one of the one or more uplinkconfigured grants on an active UL BWP. For a Type 1 uplink configuredgrant, in response to transmitting the one or more RRC messages, thebase station may activate (or (re)initialize the at least one of the oneor more uplink configured grants. For a Type 2 configured grant, a basestation may (re)initialize a periodic resource of at least one of theone or more uplink configured grants and activate the periodic resourcein response to transmitting a DCI indicating an activation. The basestation may receive a data packet from a wireless device. At step 3220,the base station may determine if the data packet is received via theperiodic resource of the at least one of the one or more uplinkconfigured grants or via a resource indicated by a dynamic uplink grant.If the data packet is received via the resource indicated by the dynamicuplink grant, the base station may not maintain a BWP inactivity timerof a DL BWP in response to receiving the data packet, and, for example,the base station may proceed to step 3230. If the data packet isreceived via the periodic resource of the at least one of the one ormore uplink configured grants, the base station may maintain a BWPinactivity timer of a DL BWP in response to receiving the data packet.For example, the base station may (re)start a BWP inactivity timer of aDL BWP in response to an active BWP being a non-default DL BWP at step3240. For example, the base station may (re)start a BWP inactivity timerof a DL BWP in response to an active BWP being a non-default DL BWP atstep 3250.

FIG. 32B shows examples of a BWP inactivity timer management of a DL BWPthat may be performed by a wireless device. In FIG. 32B, at step 3260, awireless device may receive, from a base station, one or more RRCmessages comprising configuration parameters of one or more BWPs and/orone or more uplink configured grants. The wireless device may activate(and/or (re)initialize) at least one of the one or more uplinkconfigured grants on an active UL BWP. For a Type 1 uplink configuredgrant, in response to receiving the one or more RRC messages, thewireless device may activate (or (re)initialize the at least one of theone or more uplink configured grants. For a Type 2 configured grant, awireless device may (re)initialize a periodic resource of at least oneof the one or more uplink configured grants and activate the periodicresource in response to receiving a DCI indicating an activation. Thewireless device may transmit a data packet to the base station. At step3270, the wireless device may determine if the data packet istransmitted via the periodic resource of the at least one of the one ormore uplink configured grants or via a resource indicated by a dynamicuplink grant. The wireless device transmits the data packet via theresource indicated by the dynamic uplink grant, the wireless device maynot maintain a BWP inactivity timer of a DL BWP in response totransmitting the data packet, and, for example, the wireless device mayproceed to step 3280. If the wireless device transmits the data packetis received via the periodic resource of the at least one of the one ormore uplink configured grants, the wireless device may maintain a BWPinactivity timer of a DL BWP in response to transmitting the datapacket. For example, the wireless device may (re)start a BWP inactivitytimer of a DL BWP in response to an active BWP being a non-default DLBWP at step 3290. For example, the wireless device may (re)start a BWPinactivity timer of a DL BWP in response to an active BWP being anon-default DL BWP at step 3295.

In an example embodiment, at least one configured grant may be activatedvia L1/L2 signaling (e.g., MAC CE and/or DCI in PDCCH). For example, SPS(UP SPS and/or DL SPS) may be activated via MAC CE and/or DCI. Forexample, Type 2 GF transmission/scheduling may be activated via DCI. Forexample, the activation may be performed via a RRC message/signaling.For example, a wireless device may activate Type 1 GFtransmission/scheduling in response to receiving one or more RRCmessages/signaling. The one or more RRC messages/signaling may indicateone or more transmission/scheduling parameters of the Type 1 GFtransmission/scheduling. The one or more RRC messages/signaling maycause a wireless device to configure the Type 1 GFtransmission/scheduling.

In an example embodiment, for a wireless device configured with at leastone SPS and/or Type 2 GF transmission/scheduling on an uplink BWP in acell, a BWP inactivity timer of an active DL BWP on the cell may bedisabled (not run, or stop) during a period of time when at least one ofthe at least one SPS and/or Type 2 GF transmission/scheduling isactivated. For example, if a wireless device receives a first MAC CEand/or DCI indicating an activation of at least one of the at least oneSPS and/or Type 2 GF transmission/scheduling, the BWP inactivity timermay be disabled in response to receiving the first MAC CE and/or DCI.For example, if the wireless device receives a second MAC CE and/or DCIindicating a deactivation of the at least one of the at least one SPSand/or Type 2 GF transmission/scheduling, the BWP inactivity timer maybe (re)started in response to receiving the second MAC CE and/or DCI.For example, if at least one of SPS, Type 2 GF, and Type 1 GFtransmission/scheduling on the cell is activated, the BWP inactivitytimer may remain disabled. For example, a wireless device may restartthe BWP inactivity timer in response to receiving the second controlmessage (e.g., MAC CE and/or DCI) deactivating at least one of SPS, Type2 GF, or Type 1 GF Type 1 GF transmission/scheduling.

In an example embodiment, for a wireless device configured with at leastone SPS and/or Type 2 GF transmission/scheduling on an uplink BWP in acell, a BWP inactivity timer of an active DL BWP on the cell may be setto infinite during a period of time when at least one of the at leastone SPS and/or Type 2 GF transmission/scheduling is activated. Forexample, if a wireless device receives a first MAC CE and/or DCIindicating an activation of at least one of the at least one SPS and/orType 2 GF transmission/scheduling, the BWP inactivity timer may be setto infinite in response to receiving the first MAC CE and/or DCI. Forexample, if the wireless device receives a second MAC CE and/or DCIindicating a deactivation of the at least one of the at least one SPSand/or Type 2 GF transmission/scheduling, the BWP inactivity timer maybe (re)started in response to receiving the second MAC CE and/or DCI.For example, if at least one of SPS, Type 2 GF, or Type 1 GFtransmission/scheduling on the cell is activated, the BWP inactivitytimer may remain infinite. For example, a wireless device may (re)startthe BWP inactivity timer in response to receiving the second MAC CEand/or DCI deactivating at least one of SPS, Type 2 GF, or Type 1 GFType 1 GF transmission/scheduling on the cell is not activated.

In an example embodiment, a wireless device may (re)start a BWPinactivity timer of an active DL BWP on the cell one or more timesduring a period of time when at least one of the at least one Type 1 GFtransmission/scheduling and/or Type 2 GF transmission/scheduling isactivated. For example, an active DL BWP (e.g., a current active DL BWP)may not be a default bandwidth part. A wireless device may maintain aBWP inactivity timer one or more times while the active BWP (e.g., acurrent active DL BWP) is being activated. For example, if a wirelessdevice receives a first MAC CE and/or DCI indicating an activation of atleast one of the at least one SPS and/or Type 2 GFtransmission/scheduling, a wireless device may (re)start a BWPinactivity timer in response to receiving the first MAC CE and/or DCI.For example, a wireless device may (re)start a BWP inactivity timer ofan active DL BWP at a TTI where one or more radio resources associatedwith at least one of at least one SPS and/or Type 2 GFtransmission/scheduling are assigned/allocated. For example, a wirelessdevice may transmit one or more data packet via the TTI.

For example, if a wireless device receives a MAC CE and/or DCIindicating a deactivation of the one of the at least one SPS and/or Type2 GF transmission/scheduling, the wireless device may keep a BWPinactivity timer to run without (re)starting in response to receivingthe MAC CE and/or DCI. For example, if at least one of SPS, Type 2 GF,or Type 1 GF transmission/scheduling is activated, a wireless device maykeep running a BWP inactivity timer, independent of receiving the MAC CEand/or DCI.

In an example embodiment, a wireless device may disable (or may stop, ormay not run) a BWP inactivity timer of an active DL BWP on the cellduring a period of time when the at least one Type 1 GFtransmission/scheduling is activated. For example, a wireless device mayreceive at least one first RRC message/signaling indicating anactivation of at least one of the at least one Type 1 GFtransmission/scheduling. A wireless device may disable a BWP inactivitytimer of a DL BWP with a first time offset in response to receiving theat least one RRC message/signaling. In an example, a wireless device mayreceive, from a base station, the at least one first RRCmessage/signaling comprising the first time offset. In an example, thefirst time offset may be predefined. For example, if the wireless devicereceives at least one second RRC message/signaling indicating adeactivation of the at least one of the at least one Type 1 GFtransmission/scheduling, the wireless device may (re)started the BWPinactivity timer with a second time offset in response to receiving thesecond at least one RRC message/signaling. In an example, the at leastone second RRC message/signaling comprise the second time offset. In anexample, the second time offset may be predefined.

In an example embodiment, a wireless device may set a BWP inactivitytimer of an active DL BWP to infinity during a period of time when theat least one Type 1 GF transmission/scheduling is activated for a cell.For example, a wireless device may receive at least one first RRCmessage/signaling that may cause a wireless device to activate at leastone Type 1 GF transmission/scheduling. The wireless device may set theBWP inactivity timer to infinity with a first time offset in response toreceiving the at least one RRC message/signaling. In an example, the atleast one first RRC message/signaling comprise the first time offset. Inan example, the first time offset may be predefined. For example, awireless device may receive at least one second RRC message/signalingthat may cause the wireless device to deactivate the at least one of theat least Type 1 GF transmission/scheduling. The wireless device may(re)start the BWP inactivity timer with a second time offset in responseto receiving the at least one second RRC message/signaling. In anexample, the at least one second RRC message/signaling comprise thesecond time offset. In an example, the second time offset may bepredefined.

In an example embodiment, a wireless device may (re)start a BWPinactivity timer of an active DL BWP one or more times during a periodof time when the at least one Type 1 GF transmission/scheduling isactivated. For example, an active BWP (e.g., a current active DL BWP)may not be a default bandwidth part. For example, a wireless device mayreceive at least one first RRC message/signaling that may cause thewireless device to activate at least one Type 1 GFtransmission/scheduling. The wireless device may (re)start a BWPinactivity timer with a first time offset in response to receiving theat least one RRC message/signaling. In an example, the at least onefirst RRC message/signaling comprise the first time offset. In anexample, the first time offset may be predefined. A wireless device may(re)start a BWP inactivity timer of an active DL BWP on the cell at aTTI where one or more radio resources associated with the at least oneof the at least one Type 1 GF transmission/scheduling areassigned/allocated. For example, a wireless device may transmit one ormore data packet via the TTI.

For example, there may be one or more ways that a wireless device maymaintain a BWP inactivity timer in response to receiving a controlmessage indicating a deactivation of activated configured grant. Forexample, a wireless device may receive at least one second RRCmessage/signaling that may cause the wireless device to deactivate atleast Type 1 GF transmission/scheduling. The wireless device may(re)start a BWP inactivity timer of an active DL BWP with a second timeoffset in response to receiving the second at least one RRCmessage/signaling. In an example, the at least one second RRCmessage/signaling comprise the second time offset. In an example, thesecond time offset may be predefined. For example, the wireless devicemay keep running the BWP inactivity timer without (re)starting inresponse to receiving the second at least one RRC message/signaling. Forexample, a wireless device

FIG. 33 is example diagrams illustrating scenarios starting a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure. In FIG. 33, a wireless device may start an BWP inactivitytimer in response to receiving a DCI switching an active BWP to anon-default BWP. The timer may stop or be disabled in response toreceiving a DCI activating the configured grant (SPS or Type 2 GF).During the time where the configured grant is activated, the timer maynot run. The wireless device may restart the time in response toreceiving a DCI deactivating the activated configured grant when thereis no other configured grant.

FIG. 34 is example diagrams illustrating scenarios starting a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure In FIG. 34, a wireless device may receive one or more RRCmessage/signaling configured a first and second configured grants. Thewireless device may start an BWP inactivity timer in response toreceiving a DCI switching an active BWP to a non-default BWP. The timermay stop or be disabled in response to receiving a DCI activating atleast one of the first and second configured grants (SPS or Type 2 GF).During the time where the at least one of the configured grants isactivated, the timer may not run. For example, the wireless device maynot restart the timer when the first configured grant is deactivated viaa DCI if the second configured grant is activated. The wireless devicemay restart the time in response to receiving a DCI deactivating theactivated configured grant when there is no other configured grant.

FIG. 35 is example diagrams illustrating scenarios starting a BWPinactivity timer as per an aspect of an embodiment of the presentdisclosure In FIG. 35, a wireless device and/or base station may startand/or stop (disable) a BWP inactivity timer depending onactivation/deactivation state of one or more configured grants. Forexample, if there is at least one configured grant on a cell isactivated, the timer may be running if an active BWP is not a defaultBWP. For example, if there is no activated configured grant on the cell,the timer may be independent of the activation/deactivation state of theconfigured grant.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 36 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3610, a wireless device may receive at leastone message from a base station. The at least one message may compriseconfiguration parameters. The configuration parameters may indicateperiodic resources of a configured grant. The configured grant may beconfigured in an uplink bandwidth part. The configuration parameters mayindicate a timer value of a bandwidth part inactivity timer. At 3620,the bandwidth part inactivity timer may be started in response toactivating a downlink bandwidth part. At 3630, one or more data packetsmay be transmitted via a first transmission interval of a first resourceof the periodic resources of the uplink bandwidth part. At 3640, thebandwidth part inactivity timer may be restarted at a time based on thefirst transmission interval. At 3650, in response to an expiry of thebandwidth part inactivity timer, the wireless device may switch from thedownlink bandwidth part to a default bandwidth part as an activebandwidth part.

According to an example embodiment, the downlink bandwidth part may bepaired with the uplink bandwidth part. According to an exampleembodiment, the switching the active bandwidth part from the downlinkbandwidth part to the default bandwidth part may comprise an activationof the default bandwidth part. According to an example embodiment, theswitching of the active bandwidth part from the downlink bandwidth partto the default bandwidth part may comprise a deactivation of thedownlink bandwidth part. According to an example embodiment, theconfigured grant may be a configured grant Type 1. According to anexample embodiment, the configured grant may be a configured grant Type2. According to an example embodiment, the downlink bandwidth part maybe a non-default bandwidth part. According to an example embodiment, theconfiguration parameters may indicate a first subcarrier spacing of theuplink bandwidth part. The configuration parameters may indicate a firstcyclic prefix of the uplink bandwidth part. The configuration parametersmay indicate a first number of first contiguous physical radio resourceblocks of the uplink bandwidth part. The configuration parameters mayindicate a first offset of a first physical radio resource block of thefirst contiguous physical radio resource blocks.

According to an example embodiment, he configured grant of the uplinkbandwidth part may be deactivated in response to deactivating the uplinkbandwidth part. According to an example embodiment, the configurationparameters may indicate a second subcarrier spacing of the defaultbandwidth part. The configuration parameters may indicate a secondcyclic prefix of the default bandwidth part. The configurationparameters may indicate a second number of second contiguous physicalradio resource blocks of the default bandwidth part. The configurationparameters may indicate a second offset of a second physical radioresource block of the second contiguous physical radio resource blocks.

According to an example embodiment, a first downlink control informationmay be received. The first downlink control information may comprise anuplink grant. According to an example embodiment, the first downlinkcontrol information may comprise a first identifier indicating theuplink bandwidth part. According to an example embodiment, the uplinkgrant may indicate a second resource of the uplink bandwidth part.According to an example embodiment, a second downlink controlinformation may be received. The second downlink control information maycomprise a second identifier indicating the downlink bandwidth part.According to an example embodiment, the second downlink controlinformation may comprise a downlink assignment.

According to an example embodiment, the active bandwidth part may beswitched to the downlink bandwidth part. According to an exampleembodiment, the switching of the active bandwidth part to the downlinkbandwidth part may comprise the activating the downlink bandwidth part.

According to an example embodiment, the configuration parameters mayindicate a radio network temporary identifier of the configured grant.The configuration parameters may indicate a periodicity of the periodicresources. According to an example embodiment, the configurationparameters may indicate a time offset of a resource of the periodicresources with respect to a first system frame number. According to anexample embodiment, the first system frame number may be zero.

FIG. 37 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3710, a wireless device may receive at leastone message from a base station. The at least one message may compriseconfiguration parameters indicating periodic resources of a configuredgrant. The configured grant may be configured for an uplink bandwidthpart. At 3720, a bandwidth part inactivity timer may be started inresponse to activation of a downlink bandwidth part. At 3730, one ormore data packets may be transmitted via a first transmission intervalof a first resource of the periodic resources of the uplink bandwidthpart. At 3740, the bandwidth part inactivity timer may be restarted at atime based on the first transmission interval. According to an exampleembodiment, further comprising switching an active bandwidth part fromthe downlink bandwidth part to a default bandwidth part in response toan expiry of the bandwidth part inactivity timer.

FIG. 38 may be an example flow diagram as per an aspect of an embodimentof the present disclosure. At 3810, a wireless device may start abandwidth part inactivity timer in response to activating a downlinkbandwidth part. At 3820, the wireless device may transmit one or moredata packets to a base station via a first transmission interval ofperiodic resources indicated by a configured grant of an uplinkbandwidth part. At 3830, the bandwidth part inactivity timer may berestarted at a time based on the first transmission interval. Accordingto an example embodiment, the wireless device may receive at least onemessage from the base station. The at least one message may compriseconfiguration parameters of the periodic resources of the configuredgrant. According to an example embodiment, an active bandwidth part maybe switched from the downlink bandwidth part to a default bandwidth partin response to an expiry of the bandwidth part inactivity timer.

FIG. 39 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3910, a base station may start a bandwidthpart inactivity timer for a wireless device in response to a downlinkbandwidth part being an active bandwidth part for the wireless device.At 3920, the base station may receive one or more data packets from thewireless device via a first transmission interval of periodic resourcesindicated by a configured grant of an uplink bandwidth part. At 3930,the bandwidth part inactivity timer may be restarted at a time based onthe first transmission interval.

According to an example embodiment, a second state of the downlinkbandwidth part may be switched to an active state for the wirelessdevices. According to an example embodiment, the downlink bandwidth partmay be paired with the uplink bandwidth part. According to an exampleembodiment, the configured grant may be a configured grant Type 1.According to an example embodiment, the configured grant may be aconfigured grant Type 2. According to an example embodiment, thedownlink bandwidth part may be a non-default bandwidth part. Accordingto an example embodiment, the configured grant may be switched to adeactivation state in response to switching the uplink bandwidth part toan inactive state.

According to an example embodiment, device in response to an expiry ofthe bandwidth part inactivity timer, a state of a default bandwidth partmay be switched to an active state for the wireless. According to anexample embodiment, the state of the default bandwidth part switching tothe active state may comprise switching a second state of the downlinkbandwidth part to an inactive state.

According to an example embodiment, a first downlink control informationmay be transmitted to the wireless device. The first downlink controlinformation may comprise an uplink grant for the wireless device.According to an example embodiment, the first downlink controlinformation may comprise a first identifier indicating the uplinkbandwidth part. According to an example embodiment a second downlinkcontrol information may be transmitted to the wireless device. Thesecond downlink control information may comprise a second identifierindicating the downlink bandwidth part. According to an exampleembodiment, the second downlink control information may comprise adownlink assignment. According to an example embodiment, in response tothe transmitting the second downlink control information, a second stateof the downlink bandwidth part may be switched to an active state forthe wireless device.

According to an example embodiment, the base station may transmit atleast one message to the wireless device. The at least one message maycomprise configuration parameters of the periodic resources of theconfigured grant for the wireless device. According to an exampleembodiment, the configuration parameters may indicate a first subcarrierspacing of the uplink bandwidth part. The configuration parameters mayindicate a first cyclic prefix of the uplink bandwidth part. Theconfiguration parameters may indicate a first number of first contiguousphysical radio resource blocks of the uplink bandwidth part. Theconfiguration parameters may indicate a first offset of a first physicalradio resource block of the first contiguous physical radio resourceblocks. The configuration parameters may indicate a radio networktemporary identifier of the configured grant. The configurationparameters may indicate a periodicity of the periodic resources. Theconfiguration parameters may indicate a time offset of a resource of theperiodic resources with respect to a first system frame number.According to an example embodiment, the first system frame number may bezero. According to an example embodiment, The configuration parametersmay indicate a second subcarrier spacing of a default bandwidth part.The configuration parameters may indicate a second cyclic prefix of thedefault bandwidth part. The configuration parameters may indicate asecond number of second contiguous physical radio resource blocks of thedefault bandwidth part. The configuration parameters may indicate asecond offset of a second physical radio resource block of the secondcontiguous physical radio resource blocks.

FIG. 40 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4010, a wireless device may receive a firstradio resource control message from a base station. The first radioresource control message may comprise first configuration parameters ofa cell. The first configuration parameters may comprise first bandwidthpart (BWP) configuration parameters of a default BWP. The firstconfiguration parameters may comprise second BWP configurationparameters of a first BWP. The first configuration parameters maycomprise a timer parameter for a BWP inactivity timer. At 4020, the BWPinactivity timer may be started in response to activating the first BWP.At 4030, may receive a second radio resource control message while theBWP inactivity timer is running. The second radio resource controlmessage may comprise second configuration parameters of the cell. At4040, a determination may be made that the timer parameter for the BWPinactivity timer is absent in the second configuration parameters. At4050, the BWP inactivity timer may be disabled in response to thedetermination. At 4060, in response to the disabling the BWP inactivitytimer, the first BWP may be maintained as an active BWP until thewireless device receives a first command indicating switching the activeBWP.

According to an example embodiment, the cell may be a primary cell of aplurality of cells. According to an example embodiment, the cell may bea secondary cell of a plurality of cells. According to an exampleembodiment, the first BWP configuration parameters may indicate afrequency location. The first BWP configuration parameters may indicatea bandwidth. The first BWP configuration parameters may indicate a valueof subcarrier spacing. The first BWP configuration parameters mayindicate a cyclic prefix. The first BWP configuration parameters mayindicate one or more reference signal resource configuration. Accordingto an example embodiment, a first downlink control information (DCI) maybe received. The first DCI may indicate downlink assignments or uplinkgrants on the first BWP. The first BWP may be activated in response toreceiving the first DCI. According to an example embodiment, theactivating of the first BWP may comprise monitoring a downlink controlchannel of the first BWP. According to an example embodiment, themaintaining of the first BWP as the active BWP may comprise monitoring adownlink control channel of the first BWP. The maintaining of the firstBWP as the active BWP may comprise receiving data packets based on adownlink control information received on a downlink control channel.According to an example embodiment, data packets may be received on thefirst BWP without switching to the default BWP. According to an exampleembodiment, a downlink control channel may be monitored on the first BWPin response to maintaining the first BWP as the active BWP. According toan example embodiment, the disabling of the BWP inactivity timer maycomprise stopping the BWP inactivity timer.

According to an example embodiment, the wireless device may activate thefirst BWP in response to receiving a second command indicating anactivation of the cell. According to an example embodiment, the secondcommand may comprise a medium access control control element. The secondcommand may comprise a downlink control information.

According to an example embodiment, the first command may comprise adownlink control information. According to an example embodiment, thedownlink control information may indicate switching from the first BWPto a second BWP as an active BWP. According to an example embodiment,the second BWP may be different from the default BWP.

According to an example embodiment, the wireless device may activate thefirst BWP in response to receiving one or more signals. According to anexample embodiment, the one or more signals may comprise a power controlcommand parameter. The one or more signals may comprise a CSI reportingindication. According to an example embodiment, the one or more signalsmay comprise downlink control resource set parameters. The one or moresignals may comprise uplink control channel resource set parameters.According to an example embodiment, the one or more signals may comprisesounding reference signal transmission commands. The one or more signalsmay comprise beam management parameters. According to an exampleembodiment, the one or more signals may comprise a downlink controlinformation indicating an activation of a secondary cell.

FIG. 41 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4110, a base station may transmit a firstradio resource control message to a wireless device. The first radioresource control message may comprise first configuration parameters ofa cell. The first configuration parameters comprise first bandwidth part(BWP) configuration parameters of a default BWP. The first configurationparameters comprise second BWP configuration parameters of a first BWP.The first configuration parameters comprise a timer parameter for a BWPinactivity timer of the wireless device. At 4120, a downlink controlinformation may be transmitted. The downlink control information mayindicate an activation of the first BWP for the wireless device. At4130, the base station may determine a disabling of the BWP inactivitytimer and a maintaining an active state of the first BWP for thewireless device. At 4140, a second radio resource control message may betransmitted. The second radio resource control message may comprisesecond configuration parameters of the cell. The timer parameter for theBWP inactivity timer may be absent in the second configurationparameters in response to the determination. At 4150, the BWP inactivitytimer for the wireless device may be disabled.

FIG. 42 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4210, a wireless device may receive a radioresource control message. The radio resource control message maycomprise configuration parameters of a cell. The configurationparameters may comprise first bandwidth part (BWP) configurationparameters for a first BWP. The configuration parameters may comprisesecond BWP configuration parameters for a default BWP. At 4220, thefirst BWP may be activated. At 4230, a determination may be made that aparameter for a BWP inactivity timer is absent from the configurationparameters. At 4240, in response to the determination, the BWPinactivity timer may be disabled without switching to the default BWP.At 4250, in response to disabling the BWP inactivity timer, the firstBWP may be maintained as an active BWP until the wireless devicereceives a command indicating a BWP switching.

FIG. 43 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4310, a first radio resource control (RRC)message may be received. The first RRC message may comprise firstconfiguration parameters of a cell. The first configuration parametersmay indicate a first BWP. The first configuration parameters mayindicate an initial active BWP. The first configuration parameters mayindicate a value associated with a BWP inactivity timer. At 4320, adownlink control information may be received. The downlink controlinformation may indicate downlink assignments or an uplink grant on thefirst BWP. At 4330, the BWP inactivity timer may be started with thevalue in response to the downlink control information. At 4340, a secondRRC message may be received. The second RRC message may comprise secondconfiguration parameters of the cell where the BWP inactivity timer isabsent. At 4350, in response to the BWP inactivity timer being absent inthe second RRC message the BWP inactivity timer may be stopped. Inresponse to the BWP inactivity timer being absent in the second RRCmessage, data packets may be received on the first BWP without switchingto the initial active BWP.

FIG. 44 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4410, a first radio resource control (RRC)message may be received. The first RRC message may comprise firstconfiguration parameters of a cell. The first configuration parametersmay indicate one or more bandwidth parts (BWPs) comprising at least oneof a default BWP and an initial active BWP. The first configurationparameters may indicate a value associated with a BWP inactivity timer.At 4420, a downlink control information may be received. The downlinkcontrol information indicating downlink assignments or uplink grant. At4430, the BWP timer may be started with the value in response to thedownlink control information. At 4440, a second RRC message may bereceived. The second RRC message may comprise second configurationparameters of the cell, where the value associated with the BWP timer isset to infinite. At 4450, in response to the second RRC message, the BWPtimer may be disabled. In response to the second RRC message, datapackets may be received on an active BWP of the one or more BWPs withoutswitching to the default BWP or the initial active BWP.

FIG. 45 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4510, a wireless device may receive radioresource control messages from a base station. The radio resourcecontrol messages may comprise configuration parameters of a cell. Theconfiguration parameters may comprise first radio resource parameters ofbandwidth parts (BWPs) comprising a first BWP. The configurationparameters may comprise second radio resource parameters of referencesignals. At 4520, a downlink control information may be received. Thedownlink control information may indicate switching to the first BWP asan active BWP. At 4530, the first BWP may be activated in response tothe downlink control information. At 4540, in response to activating thefirst BWP, one or more reference signal received power (RSRP) reportsfor the first BWP may be transmitted. The one or more RSRP reports maycomprise a reference signal index indicating one of the referencesignals.

According to an example embodiment, the cell may be a primary cell of aplurality of cells. According to an example embodiment, the cell may bea secondary cell of a plurality of cells. According to an exampleembodiment, the first radio resource parameters of the BWPs may comprisea frequency location. The first radio resource parameters of the BWPsmay comprise a bandwidth. The first radio resource parameters of theBWPs may comprise a value of subcarrier spacing. The first radioresource parameters of the BWPs may comprise a cyclic prefix. Accordingto an example embodiment, the downlink control information may indicateswitching from a second BWP to the first BWP as the active BWP.According to an example embodiment, the activating of the first BWP maycomprise monitoring a downlink control channel on the first BWP.According to an example embodiment, the one or more RSRP reports may beobtained based on measurements of the reference signals. According to anexample embodiment, the reference signals may comprise one or morechannel state information reference signals. The reference signals maycomprise one or more synchronization signal blocks.

FIG. 46 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4610, a wireless device may activate a firstbandwidth part in response to switching to the first bandwidth part asan active bandwidth part. At 4620, in response to the activating thefirst bandwidth part, one or more reference signal received powerreports for the first bandwidth part may be transmitted. The one or morereference signal received power reports may comprise a reference signalindex indicating reference signals. The one or more reference signalreceived power reports may comprise a value of reference signal receivedpower of the reference signals.

FIG. 47 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4710, a base station may transmit radioresource control messages to a wireless device. The radio resourcecontrol messages may comprise configuration parameters of a cell. Theconfiguration parameters may comprise first radio resource parameters ofbandwidth parts (BWPs) comprising a first BWP. The configurationparameters may comprise second radio resource parameters of referencesignals. At 4720, a downlink control information may be transmitted. Thedownlink control information may indicate switching to the first BWP asan active BWP for the wireless device. At 4730, the first BWP may beswitched to an active state for the wireless device. At 4740, inresponse to the switching the first BWP, one or more reference signalreceived power (RSRP) reports for the first BWP may be received from thewireless device. The one or more RSRP reports may comprise a referencesignal index indicating one of the reference signals.

FIG. 48 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4820, a base station may switch a firstbandwidth part to an active state for a wireless device. At 4820, inresponse to the switching to the first bandwidth part, one or morereference signal received power reports for the first bandwidth part maybe received from the wireless device. The one or more reference signalreceived power reports may comprise a reference signal index indicatingreference signals. The one or more reference signal received powerreports may comprise a value of reference signal received power of thereference signals.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” or “one or more.” Similarly, any term thatends with the suffix “(s)” is to be interpreted as “at least one” or“one or more.” In this disclosure, the term “may” is to be interpretedas “may, for example.” In other words, the term “may” is indicative thatthe phrase following the term “may” is an example of one of a multitudeof suitable possibilities that may, or may not, be employed to one ormore of the various embodiments. If A and B are sets and every elementof A is also an element of B, A is called a subset of B. In thisspecification, only non-empty sets and subsets are considered. Forexample, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and{cell1, cell2}. The phrase “based on” is indicative that the phrasefollowing the term “based on” is an example of one of a multitude ofsuitable possibilities that may, or may not, be employed to one or moreof the various embodiments. The phrase “in response to” is indicativethat the phrase following the phrase “in response to” is an example ofone of a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments. The terms“including” and “comprising” should be interpreted as meaning“including, but not limited to.”

In this disclosure and the claims, differentiating terms like “first,”“second,” “third,” identify separate elements without implying anordering of the elements or functionality of the elements.Differentiating terms may be replaced with other differentiating termswhen describing an embodiment.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (Information elements: IEs) may compriseone or more objects, and each of those objects may comprise one or moreother objects. For example, if parameter (IE) N comprises parameter (IE)M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) Kcomprises parameter (information element) J, then, for example, Ncomprises K, and N comprises J. In an example embodiment, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: transmitting, by a basestation to a wireless device via a physical downlink control channel(PDCCH), a downlink control information (DCI) indicating for thewireless device to switch from a second bandwidth part (BWP) to a firstBWP as an active BWP; and receiving, in response to the first BWP beingactivated, a reference signal received power (RSRP) report for the firstBWP, wherein the RSRP report comprises: a reference signal indexindicating a reference signal of the first BWP; and a value of an RSRPof the reference signal.
 2. The method of claim 1, further comprisingtransmitting, to the wireless device, one or more radio resource control(RRC) messages indicating parameters of: a first PDCCH and the referencesignal, both corresponding to the first BWP; and the PDCCH and a secondreference signal, both corresponding to the second BWP.
 3. The method ofclaim 2, wherein the parameters are configuration parameters of aprimary cell of a plurality of cells.
 4. The method of claim 2, whereinthe parameters are configuration parameters of a secondary cell of aplurality of cells.
 5. The method of claim 2, wherein the one or moreRRC messages further indicate BWP parameters comprising at least one of:a frequency location; a bandwidth; a value of subcarrier spacing; or acyclic prefix.
 6. The method of claim 2, further comprising receiving,from the wireless device and in response to the one or more RRCmessages, a radio resource management (RRM) report based on ameasurement of a synchronization signal/physical broadcast channel(SS/PBCH) block or a channel state information reference signal(CSI-RS).
 7. The method of claim 1, further comprising: transmitting afirst DCI via a first PDCCH; and transmitting a first transport block,based on the first DCI, via the first BWP.
 8. The method of claim 1,wherein the value of the RSRP of the reference signal is based on ameasurement of the reference signal.
 9. The method of claim 1, whereinthe reference signal comprises at least one of: one or more channelstate information reference signals; or one or more synchronizationsignal blocks.
 10. The method of claim 1, further comprisingtransmitting, to the wireless device, a first PDCCH via the first BWPbased on the first BWP being activated.
 11. A base station comprising:one or more processors; and memory storing instructions that, whenexecuted by the one or more processors, cause the base station to:transmit, to a wireless device via a physical downlink control channel(PDCCH), a downlink control information (DCI) indicating for thewireless device to switch from a second bandwidth part (BWP) to a firstBWP as an active BWP; and receive, in response to the first BWP beingactivated, a reference signal received power (RSRP) report for the firstBWP, wherein the RSRP report comprises: a reference signal indexindicating a reference signal of the first BWP; and a value of an RSRPof the reference signal.
 12. The base station of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe base station to transmit, to the wireless device, one or more radioresource control (RRC) messages indicating parameters of: a first PDCCHand the reference signal, both corresponding to the first BWP; and thePDCCH and a second reference signal, both corresponding to the secondBWP.
 13. The base station of claim 12, wherein the parameters areconfiguration parameters of a primary cell of a plurality of cells. 14.The base station of claim 12, wherein the parameters are configurationparameters of a secondary cell of a plurality of cells.
 15. The basestation of claim 12, wherein the one or more RRC messages furtherindicate BWP parameters comprising at least one of: a frequencylocation; a bandwidth; a value of subcarrier spacing; or a cyclicprefix.
 16. The base station of claim 12, wherein the instructions, whenexecuted by the one or more processors, further cause the base stationto receive, from the wireless device and in response to the one or moreRRC messages, a radio resource management (RRM) report based on ameasurement of a synchronization signal/physical broadcast channel(SS/PBCH) block or a channel state information reference signal(CSI-RS).
 17. The base station of claim 11, wherein the instructions,when executed by the one or more processors, further cause the basestation to: transmit a first DCI via a first PDCCH; and transmit a firsttransport block, based on the first DCI, via the first BWP.
 18. The basestation of claim 11, wherein the value of the RSRP of the referencesignal is based on a measurement of the reference signal.
 19. The basestation of claim 11, wherein the reference signal comprises at least oneof: one or more channel state information reference signals; or one ormore synchronization signal blocks.
 20. The base station of claim 11,wherein the instructions, when executed by the one or more processors,further cause the base station to transmit, to the wireless device, afirst PDCCH via the first BWP based on the first BWP being activated.